# tags

**URL:** <https://forum.ansible.com/t/tags/15771>\
**Category:** Ansible Project\
**Created:** [July 24, 2014, 7:52pm UTC](https://forum.ansible.com/t/tags/15771 "2014-07-24T19:52:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_Dur](https://avatars.discourse-cdn.com/v4/letter/m/a6a055/32.png) [@Michael\_Dur](https://forum.ansible.com/u/Michael_Dur)\
**Post date:** [July 24, 2014, 7:52pm UTC](https://forum.ansible.com/t/tags/15771/1 "2014-07-24T19:52:17Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [July 24, 2014, 10:53pm UTC](https://forum.ansible.com/t/tags/15771/2 "2014-07-24T22:53:17Z")

</div>

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.