The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
Precedence of various environment setting methods should change.
|Affected Puppet version:||0.25.0||Branch:|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
This ticket may be automatically exported to the PUP project on JIRA using the button below:
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.
#2 Updated by Luke Kanies almost 5 years ago
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.