You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tags are a core feature of Puppet. I use them to filter resources in a catalog to optimize long builds.
Describe the Solution You Would Like
Both bolt apply and the apply function take parameters to enable noop mode. It should be extended to take a tags parameter.
Describe Alternatives You've Considered
I considered refactoring my code to eliminate tags, but my use case doesn't support that. For workarounds, I tried setting the global tags setting like:
run_command('puppet config set tags foo', $target)
apply($target) { include module }
run_command('puppet config delete tags', $target)
and though I could see the tags = foo setting present on the target's main puppet.conf, it did not take effect during the apply block. A "working" but ugly workaround was to configure tags directly in the interpreter:
Use Case
Tags are a core feature of Puppet. I use them to filter resources in a catalog to optimize long builds.
Describe the Solution You Would Like
Both
bolt apply
and theapply
function take parameters to enablenoop
mode. It should be extended to take atags
parameter.Describe Alternatives You've Considered
I considered refactoring my code to eliminate tags, but my use case doesn't support that. For workarounds, I tried setting the global tags setting like:
and though I could see the
tags = foo
setting present on the target's mainpuppet.conf
, it did not take effect during the apply block. A "working" but ugly workaround was to configure tags directly in the interpreter:inventory.yaml
The text was updated successfully, but these errors were encountered: