Use resource only if a tag is given at the command line

[Karsten Heymann]

Hi puppet users,

is there an easy way to enable a resource only if a certain tag is given? Something like "refreshOnly", but for tags? I'm aware of --skip_tags, but that would require us to specify that on every normal run where the resource is not wanted. 

Best regards

Karsten

[Martin Alfke]

Hi Karsten,

you can introduce a fact and provide the fact on cli when starting the puppet agent run:

In your Puppet code:

if $facts['foo'] {

  package { 'foo'

    ensure => 'latest',

  }

}

On CLI:

FACTER_foo=true puppet agent --test

I hope that this a solution which is working for you.

Best,

Martin

--

You received this message because you are subscribed to the Google Groups "Puppet Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/3659636e-13c4-455f-98c2-d77a6b79f323%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[jcbollinger]

On Friday, January 18, 2019 at 7:08:21 AM UTC-6, Karsten Heymann wrote:

Hi puppet users,

is there an easy way to enable a resource only if a certain tag is given? Something like "refreshOnly", but for tags? I'm aware of --skip_tags, but that would require us to specify that on every normal run where the resource is not wanted. 

No, not as such.  The CLI provides for using tags to limit the resources applied to a subset of those in the node's catalog, but this does cannot cause resources to be included in the catalog that otherwise would not be.  That does not really fit with the Puppet architecture, for tags are a property of declared classes and resources.  Or you can look at it as tags being class and resource metadata belonging to the catalog in which they appear (as opposed to being inherent in the classes and resources themselves).  As such, you can manipulate a catalog based on tags once it is built, but you cannot use them to cause the catalog to be built differently in the first place.  You especially cannot use them to cause a resource to be included that ordinarily would not be, because resources only have tags on the context of a catalog to which they already have been added.

John