Playbook should be split into some atomic tasks #12
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Some of the tasks in the playbook don't need to run every time. ie, user provisioning.
So, we should keep site.yml as being the play of all play, but break down the users into an atomic play, break down the webserver stuff atomically, and probably packages.
What is the best approach to doing just this. User creation for sure should be separate.. But not sure how much else should be separated out.
I think by web server configs (web/gopher/etc, in one go), user management, and maybe shell-server required things. ie, I can update web front end, or new/removed users, or fix up the environment for people to log in.
Past that is an exercise, if you want, to break everything into atomic tasks, that eventually roll into one master playbook, to rebuild the entire server (Should the need arise)
How does that work with ansible. I seem to be somewhat grasping what is currently setup. But not sure the best way things could be split up. Should it just be more files like the site.yml that only runs portions of the ansible script instead of all of it. Or is it done in some other way. Sorry very green when it comes to ansible.