Yes V2 is usable to a degree - it's passing about 75% of the integration tests we have but it's definitely not finished. You can use it very simply by sourcing v2/hacking/env-setup, just as you would with a regular git checkout of the code.
If you try it out and hit a bug, let us know here on the mailing list first before opening a GitHub issue, as we're still tracking things internally and may know about it already. Thanks! On Tue, Jan 27, 2015 at 3:34 PM, Grzegorz Nosek <[email protected]> wrote: > Hi, > > I'm happy v2 will include equivalent features in the core (please add > sudo/sudo_user/remote_user while you're at it). I acknowledge this module > is a hack and would be better handled internally, but it does allow for > less repetition in playbooks and solves a pain point of mine. > > Is v2 usable to any degree? Are the new features/changes documented > somewhere? Unfortunately I won't attend AnsibleFest but I'm looking forward > to your slides/video. > > Thanks, > Grzegorz Nosek > > W dniu wtorek, 27 stycznia 2015 21:05:39 UTC+1 użytkownik James Cammarata > napisał: >> >> Hi Grzegorz, >> >> You might want to look at the v2 work going on, which will implement some >> of the features you've noted above (include + with_items and runtime >> evaluated includes, at least at the task level). >> >> Also, another feature we're working on in v2 is the concept of "blocks", >> which will essentially allow better grouping (and error handling) for >> tasks. An example of a block is: >> >> begin: >> - name: task 1 >> ... >> - name: task 2 >> ... >> rescue: >> - name: rescue task 1 (runs when any task in the main block fails) >> ... >> end: >> - name: some cleanup task that is always run >> ... >> >> Blocks already support tags/when statements, but do not currently support >> many of the other task-level options like sudo/sudo_user. If we want to, >> they could be extended to include those as well without too much effort I >> think, if that's something users are interested in. We're using the >> ruby-ish syntax here due to internal variable names, but we have talked >> about switching this back to the more pythonic try/except/finally syntax. >> >> I plan on using my speaking slot for AnsibleFest London next week to run >> over the new features in V2, so stay tuned for a slide deck to see what >> else is going on in the new codebase (or even better, buy tickets!). >> >> Sorry this degenerated into a "hey, look at v2!" response, but I really >> do think it does (or will) fit what you're trying to accomplish here, and >> we're getting very close to opening up contributions there as it's nearing >> critical mass on feature support. >> >> Thanks! >> > -- > 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/69924c97-0eb6-4f4d-a382-03204ac9041a%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/69924c97-0eb6-4f4d-a382-03204ac9041a%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/CAMFyvFhur8GzNY%3DixNqEWLqUE7eDQAXwCQ6rHBLTc3yQXPWhQg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
