| Puppet Version: 4.4 through 5.5 and HEAD
Puppet Server Version: n/a
OS Name/Version: all We were extremely grateful to see skip_tags added as a configuration option. This has been tremendously useful. However in practice we've started to see problems when multiple teams make use of the tag for different purposes. Example: skip_tags = monitoring_changes,app_deploy These tags are used by two different teams to limit changes to things the other team are unaware of, and not responsible for managing. Desired Behavior: If tags includes a tag in skip_tags then it should override that tag individually, rather than requiring the entire skip tags to be provided sans the one tag. So if this command is run: puppet agent --test --tags app_deploy It should not make monitoring changes, and vice versa. Actual Behavior: A person must lookup the current skip_tags and remove the desired tag. This is a manual process that involves some human failures as skip_tags can vary from node to node. It also makes automation tricky.
grep skip_tags /etc/puppetlabs/puppet/puppet.conf | split -d= -f2 | awk...
|
|
