Issue #2322 has been updated by Luke Kanies.
Been thinking about this, and it's a bit hard - the Settings are essentially a black box, and we normally don't know or care how a given value was arrived at, whether by a default value or via the CLI/config. Here, you're asking that we start to care about that, by providing visibility into how a value was provided. This doesn't mean that it's impossible, it just means we need to extend Settings so we can tell if we've got a default value or a different value, so we can behave differently as a result. Yuck. ---------------------------------------- Feature #2322: Precedence of various environment setting methods should change. http://projects.reductivelabs.com/issues/2322 Author: Nigel Kersten Status: Accepted Priority: Normal Assigned to: Category: Target version: 0.25.0 Complexity: Unknown Affected version: 0.25.0 Keywords: Currently if you provide your environment via a fact it overrides anything in your configuration file or via the command line. I suggest that the value as provided by a fact should be overriden by a command line option. I'm assuming command line options trump config file options, so I suggest the order of precedence should be: command line options config file options fact value I'm putting this in for 0.25.x as I don't see the benefit in changing this behavior for 0.24.x at this stage. -- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
