> To achieve what I'm after do I need to refactor all the roles so that
they have
To answer my own question, No.
I do need to change the way the roles are called
instead of
- hosts: tag_compute-node
roles:
- {role: 'compute', tags: 'compute'}
- {role: 'mount_smb', tags: 'mount_smb'}
- hosts:
> For me, 6 out of 6 gave the answer I expected. It's just logic and common
sense.
I recently started using ansible, and I'm trying to adapt the existing
playbooks so I can have a 'config update' run, and it is exactly how I
wanted it to behave.
config-update.yml
---
- hosts: tag_compute-node
On Wednesday, February 6, 2019 at 2:14:57 AM UTC+11, Kai Stian Olstad wrote:
>
> On 04.02.2019 04:10, Igor Cicimov wrote:
> > On Monday, February 4, 2019 at 12:10:51 AM UTC+11, Kai Stian Olstad
> > wrote:
>
> Probably pretty useless to answer but anyway.
>
You are right it was useless.
>
On 04.02.2019 04:10, Igor Cicimov wrote:
On Monday, February 4, 2019 at 12:10:51 AM UTC+11, Kai Stian Olstad
wrote:
Probably pretty useless to answer but anyway.
On 03.02.2019 01:53, Igor Cicimov wrote:
> Kai, why would I use vars when I already have tags on my tasks which
> purpose, and
On Monday, February 4, 2019 at 12:10:51 AM UTC+11, Kai Stian Olstad wrote:
>
> On 03.02.2019 01:53, Igor Cicimov wrote:
> > Kai, why would I use vars when I already have tags on my tasks which
> > purpose, and only purpose, is filtering during execution?
>
> Filtering is done on the command
On 03.02.2019 01:53, Igor Cicimov wrote:
Kai, why would I use vars when I already have tags on my tasks which
purpose, and only purpose, is filtering during execution?
Filtering is done on the command line with --tags not inside a playbook
or task file.
If you need any other functionality,
Kai, why would I use vars when I already have tags on my tasks which
purpose, and only purpose, is filtering during execution?
Also as I said back in 2015
https://groups.google.com/d/msg/ansible-project/WimzDEJLHJc/9U10Yjb4CQAJ it
is hard to retrofit variables into hundreds of playbooks you
On 02.02.2019 05:39, Igor Cicimov wrote:
Brian, I find the current usage of "tags" when calling a role via
"roles:"
or "include_role/import_role" is counter intuitive. The reason we tag
tasks
in our playbooks is for the purpose of filtering which we would expect
to
be the case in the above
Brian, I find the current usage of "tags" when calling a role via "roles:"
or "include_role/import_role" is counter intuitive. The reason we tag tasks
in our playbooks is for the purpose of filtering which we would expect to
be the case in the above mentioned scenarios as well. But it is not,
No, it is not possible
--
Brian Coca
--
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-project+unsubscr...@googlegroups.com.
To post to this
Anyone knows if this is possible in any ansible release?
On Thursday, December 17, 2015 at 8:08:14 AM UTC+11, Igor Cicimov wrote:
>
> This sounds like very reasonable request, option like:
>
> - { role: A, skip-tags: [t1, t2] }
>
> whould be very useful in case of playbook with many roles having
Is this feature implemented yet? Does somebody know anything about it?
2015. december 18., péntek 0:48:06 UTC+1 időpontban Igor Cicimov a
következőt írta:
>
> Yeah, for sure there can be some workarounds but very tedious ones. Your
> example can work but needs to be thought of at the very
Hi,
Am 11.07.2014 um 21:30 Uhr schrieb Dmitry Makovey:
On Wednesday, July 9, 2014 4:50:55 PM UTC-6, Michael DeHaan wrote:
I'm asking is something more like:
{ role: roleA, use-tags: tagY } which would be similar to the CLI
"--tags" except localized down to a roleA only and exectuting *only*
I agree that I'd like to be able to have roll contain a number of tasks and
then have then selective run. A use-tags or play-tags option would be nice
to use in that case. While you can certainly implement that with vars (see
#2 below), it seems that a tags solution would be more elegant.
I think I'd be open to it, depending on patch complexity.
On Fri, Jul 11, 2014 at 3:30 PM, Dmitry Makovey droopy4...@gmail.com
wrote:
On Wednesday, July 9, 2014 4:50:55 PM UTC-6, Michael DeHaan wrote:
Now the other question: would it be reasonable to ask for such feature
then?
It would
Excerpts from Dmitry Makovey's message of 2014-07-08 18:49:22 -0400:
Hi everybody,
http://docs.ansible.com/playbooks_tags.html mentions several ways to use
tags, one of which is:
- { role: A, tags: [t1, t2] }
This doesn't do what you think it does. It applies tags 't1' and 't2'
to all
Correct.
Tags in playbooks apply tags to tasks.
--tags means run the things that are so tagged
--skip-tags means the opposite
On Wed, Jul 9, 2014 at 9:47 AM, C. Morgan Hamill cham...@wesleyan.edu
wrote:
Excerpts from Dmitry Makovey's message of 2014-07-08 18:49:22 -0400:
Hi everybody,
On Wednesday, July 9, 2014 1:49:16 PM UTC-6, Michael DeHaan wrote:
Correct.
Tags in playbooks apply tags to tasks.
--tags means run the things that are so tagged
--skip-tags means the opposite
darn. May I suggest some clarification for the documentation then? The way
it is written
Now the other question: would it be reasonable to ask for such feature
then?
It would not :)
I think it makes much more sense to explicitly tag things.
For instance, think of flickr.com and I tag all pictures in an album
vacation, I don't have the ability to take another album and tag pictures
19 matches
Mail list logo
