Working in an environment where we hope to reuse common playbooks and roles across the organisation, I've been thinking a lot on how to manage updates to roles and playbooks without breaking repeatability (running the same playbook against the same environment should have the same result, even if the two runs are separated by months).
My current strategy and some of the techniques that I use to augment that is described at http://willthames.github.io/2014/08/11/techniques-for-versioning-ansible.html and I plan to add some more rules for ansible-lint to allow checking that roles fit the techniques (I'm not sure even whether to publish the rules, but they certainly won't be core rules as they may well be entirely specific to my environment) Anyway thoughts are welcome on whether there are better ways to do it! (Particularly if there's a pure DVCS way that achieves a similar outcome) Will -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/100fd0dc-c083-4bd3-8e9f-dce0cb2c9b18%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
