" It just seems you might want to "tag" a playbook as having a certain
category of functionality."
You can tag individual plays, but not whole playbooks. Should be
good enough.
This will apply he the tag to all tasks (whether in roles or not) therein.
On Thu, Jun 19, 2014 at 1:25 PM, Marc P
Turns out I make most of technical decisions based on spite:)
But plays in playbooks can be tagged which are in turn composed of roles
and tasks. It just seems you might want to "tag" a playbook as having a
certain category of functionality. Basically I need to do this because I
am trying to
Yes. Spite.
Tasks are tagged (roles collect tasks), not playbooks.
On Fri, May 30, 2014 at 9:52 AM, Marc Petrivelli
wrote:
> Is there any reason why I can't apply a tag to a playbook include? I have
> the following:
>
> - { include: dhcpservers.yml tags=dhcp, when: ansible_system == 'Linux'
Is there any reason why I can't apply a tag to a playbook include? I have
the following:
- { include: dhcpservers.yml tags=dhcp, when: ansible_system == 'Linux' }
but the dhcp tag seems to be ignored. Am I missing something? Does this
work for other people?
--
You received this message bec
