tags

[Michael Dur]

I notice when you try use a tag that does not exist ansible happily prints those that do exist in the error output.

Would it be possible/desirable to have an option to just print the tags on demand?  How about a tree of playbooks by tags (think of the output of the utility tree)?

Our infrastructure is complicated, and we are beginning to get lots of tags going on.

[Michael DeHaan]

A --list-tags would be a fine thing to have.

We were waiting on some refactoring to make some of the playbook parsing classes a bit more usable for that, though it actually might not be terribly difficult.

Really I want a way to compile a playbook down to a list of task objects w/o executing them.

Right now that doesn't quite fit for /usr/bin/ansible-playbook (the script) though so it needs a little bit of cleanup first.

Though I'll admit - Runner is our first target, so this may be a while.

I'd use the "specify an invalid tag" hack for now.

--
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 ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/df2cd839-e971-4848-9f13-b01a03dc23fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.