Hi interesting read, I especially liked the "uninstaller" Part, as Ansible is really not great at undoing a thing ^^, one really has to come up with a strategy for that.
Of course in "the Cloud" you can easily get away with throwing out the whole System and simply redeploying it, but for those cases where one is not yet fully cloud ready or State is just to brittle, migration, or uninstall Playbooks are useful. 👍
I would like to add, to also ensure your plays are check_mode compatible, and not only idempotent, this greatly improves the trust and confidence in your Playbooks as you can do a --check and get an Idea for what Changes will be introduced via your Playbooks.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi interesting read, I especially liked the "uninstaller" Part, as Ansible is really not great at undoing a thing ^^, one really has to come up with a strategy for that.
Of course in "the Cloud" you can easily get away with throwing out the whole System and simply redeploying it, but for those cases where one is not yet fully cloud ready or State is just to brittle, migration, or uninstall Playbooks are useful. 👍
I would like to add, to also ensure your plays are
check_modecompatible, and not only idempotent, this greatly improves the trust and confidence in your Playbooks as you can do a--checkand get an Idea for what Changes will be introduced via your Playbooks.