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
Currently there isn't many Ansible roles so it won't take long to get in the habit of it now, rather than later.
The current rules in ansible/roles should be moved to public repos and installed via ansible-galaxy such as ansible-galaxy install -r requirements.yml -p roles/. That directory would then be gitignored
It means any contributors can work on roles themselves, without getting bogged down in the entire repo. It also means you can have testing on each role individually using molecule.
The primary purpose of this is if you install external roles, there is absolutely no point having your own copy which can be outdated easily. If you want to keep the two separate, you can make an external_roles folder but this requires a custom Ansible config file.
You can disregard this if you intend to never install an external role
Currently there isn't many Ansible roles so it won't take long to get in the habit of it now, rather than later.
The current rules in
ansible/roles
should be moved to public repos and installed viaansible-galaxy
such asansible-galaxy install -r requirements.yml -p roles/
. That directory would then be gitignoredIt means any contributors can work on roles themselves, without getting bogged down in the entire repo. It also means you can have testing on each role individually using molecule.
The primary purpose of this is if you install external roles, there is absolutely no point having your own copy which can be outdated easily. If you want to keep the two separate, you can make an
external_roles
folder but this requires a custom Ansible config file.You can disregard this if you intend to never install an external role
The requirements.yml file would look like this:
The text was updated successfully, but these errors were encountered: