You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file's name is designed to be random in order to avoid being queried from outside. However as of now its name is hardcoded in the repo.
Instead, a random filename could be generated and stored in a local configuration file when executing a play-init-* playbook, and then used when actually deploying the servers. Some jinja2 code can be written to generate random strings. Would this be a good approach?
The text was updated successfully, but these errors were encountered:
This file's name is designed to be random in order to avoid being queried from outside. However as of now its name is hardcoded in the repo.
Instead, a random filename could be generated and stored in a local configuration file when executing a play-init-* playbook, and then used when actually deploying the servers. Some jinja2 code can be written to generate random strings. Would this be a good approach?
The text was updated successfully, but these errors were encountered: