The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #2322

Precedence of various environment setting methods should change.

Added by Nigel Kersten about 5 years ago. Updated about 3 years ago.

Status:AcceptedStart date:06/03/2009
Priority:LowDue date:
Assignee:-% Done:

0%

Category:-
Target version:3.x
Affected Puppet version:0.25.0 Branch:
Keywords:

We've Moved!

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:


Description

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.

History

#1 Updated by James Turnbull about 5 years ago

  • Status changed from Unreviewed to Accepted
  • Target version set to 0.25.0

#2 Updated by Luke Kanies about 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.

Yuck.

#3 Updated by Luke Kanies about 5 years ago

I’m tempted to bump this ticket, as it’s actually pretty complex and I’m not sure it’s worth holding up 0.25 for.

Nigel, do you need this enough that you’re maybe willing to spend some dev time on it?

#4 Updated by Nigel Kersten about 5 years ago

  • Target version changed from 0.25.0 to 2.6.0

It’s a “nice-to-have” issue for me. Not critical at all. Lets bump it.

I’m willing to spend dev time on it, but I think there are other things that are more important.

bumped to 0.26

#5 Updated by James Turnbull over 4 years ago

  • Target version changed from 2.6.0 to 2.7.x

#6 Updated by Nigel Kersten about 3 years ago

  • Priority changed from Normal to Low
  • Target version changed from 2.7.x to 3.x

Also available in: Atom PDF