Issue #4974 has been updated by Matt Robinson. Status changed from Accepted to Needs design decision
It sounds like we want the basic functionality described, but we're not sure how we'd like to implement it. Nigel, do you want to make that decision, or does this need more discussion? It sounds like most people would be happy if there was an "all" tag on all resources that could be used? ---------------------------------------- Bug #4974: Need a method of overriding config file tags specification with puppetd. https://projects.puppetlabs.com/issues/4974 Author: Tim Nicholas Status: Needs design decision Priority: Normal Assignee: Nigel Kersten 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.
