-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EPIC: Improve our use of ansible to use best practices #2492
Comments
|
As long as you don't expect it all done by tomorrow - I am willing to invest time in this - building on my experience as I redo AIX playbooks - on a parallel path. |
I'd love to help too! Though maybe that goes without saying.. |
We should also define what 'best practices' are (if there does not already exists a wiki page somewhere). For starters, I like @Willsparker's encouragement of idempotency (for roles which we do not already do it) in #2373 Some others
|
Funny you mention that, @Haroon-Khel , a wiki page does exist! That sort of goes into the nitty-gritty of 'best practices' (i.e. playbook structure, inventory structure etc.), but the best way to put it is, the playbooks need to be idempotent, modular and easily human-readable. I recently made a small playbook that sets up Nagios-Core for #2445 , with these in things mind. Other things, maybe more specific to Adopt, is to not use |
|
From the wiki page @Willsparker mentioned - imho: a good start for re-structuring the Unix playbooks will be using something suggested here: https://docs.ansible.com/ansible/2.8/user_guide/playbooks_best_practices.html#id24 |
Related: #1757 |
Quite a lot of our ansible use has been "improvised" over the years. We should revisit areas where we see improvements that can be made and try and "do the right thing" in each case to become a shining example of how to use ansible!
The text was updated successfully, but these errors were encountered: