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

Feature #5218

Invalid settings in config blocks should produce a warning.

Added by Nigel Kersten over 3 years ago. Updated over 1 year ago.

Status:AcceptedStart date:11/06/2010
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Affected Puppet version: Branch:
Keywords:usability

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

We only have a handful of configuration parameters that actually have any effect in an environment [block], modulepath, manifest and … maybe that’s it?

We should emit a warning when people use other parameters inside an environment block, as it’s difficult to work out what actually has any effect.

[update] – We should really do this for all config blocks. We need to make each parameter aware of the blocks in which it is appropriate.

History

#1 Updated by James Turnbull over 3 years ago

  • Status changed from Unreviewed to Needs Decision
  • Assignee set to Nigel Kersten

#2 Updated by Nigel Kersten over 3 years ago

  • Status changed from Needs Decision to Accepted
  • Assignee deleted (Nigel Kersten)
  • Target version set to 2.7.x
  • Keywords set to usability

#3 Updated by Nigel Kersten over 3 years ago

  • Subject changed from Invalid settings in environments should produce a warning. to Invalid settings in config blocks should produce a warning.

#4 Updated by Andrew Parker over 1 year ago

  • Target version deleted (2.7.x)

Also available in: Atom PDF