So, let's not go down that lint-discussion road again. We know where it leads.
Rather, let's once again discuss how we can improve roles to do what we need. As for role versioning, there have been a few who have liked the things that chef did with their library tool (I haven't used it), and we've posted quite a few times that we're open to making the ansible-galaxy CLI work better with raw SCM repos as well as versioning deps. There's also been the suggestion that ansible have a tag to assert the required ansible version, or perhaps it's a module. All of this seems like a good thing to do. I don't particularly care for the idea of requiring a version in the role name, as that breaks the ability to cleanly branch the role in Galaxy, which is handled via git tags presently. On Mon, Aug 11, 2014 at 8:45 AM, Will Thames <[email protected]> wrote: > 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 > <https://groups.google.com/d/msgid/ansible-project/100fd0dc-c083-4bd3-8e9f-dce0cb2c9b18%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CA%2BnsWgwjP1Eu3QveB1jcWAxiJXE3WSWxm7h1T%3DggR20LK%3DYmoQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
