Issue #4974 has been updated by Nigel Kersten. Status changed from Needs design decision to Accepted Assignee deleted (Nigel Kersten)
We are going to implicitly tag *all* classes and resources (everything that is taggable) with the special keyword "all". To get the functionality as described in the original bug report, you would run with "--tags=all" ---------------------------------------- Bug #4974: Need a method of overriding config file tags specification with puppetd. https://projects.puppetlabs.com/issues/4974 Author: Tim Nicholas Status: Accepted Priority: Normal Assignee: Category: Target version: Affected Puppet version: 2.6.2 Keywords: Branch: Currently, so far as I can tell, if tags=x,y is specified in the /etc/puppet/puppet.conf then there is no way to override that setting to run the full manifest. You can get close under some situations with "--tags main", but that doesn't inherit upwards from the node definition. Anything defined in 'basenode' (as inherited via "node <nodename> inherits basenode {...}") doesn't get executed. There isn't any documentation of the 'main' tag, so maybe "--tags main" is behaving as it should, but there should be some way of saying 'run everything'. Options could include a special ALL tag, changing the behaviour of the 'main' tag or introducing an --alltags command line option. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
