Bug #4826

It is difficult to verify that options don't overlap

Added by Paul Berry over 1 year ago. Updated 2 months ago.

Status:Closed Start date:09/22/2010
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:testing
Target version:-
Affected Puppet version:2.6.0 Branch:
Keywords:
Votes: 0

Description

Bug #4822 arose because we inadvertently had a global “-o” option (—onetime) which overlapped with an application-specific “-o” option (puppet doc’s —outputdir), and the was getting resolved incorrectly. Jesse and I fixed it by changing the resolution so that application-specific options take precedence over global options.

We also manually verified that there are no other options conflicts in the system. But it would be easy for an options conflict to arise in the future without anyone noticing. It would be nice if our spec tests had a way to verify that there were no options conflicts between global and application-specific options, so that we don’t inadvertently introduce bugs like #4822 in the future.

History

#1
Updated by Joshua Lifton 5 months ago

  • Assignee deleted (Paul Berry)

This issue was assigned to a former Puppet Labs employee. Adding back to the pool of unreviewed issues.

#2
Updated by Ben Hughes 4 months ago

  • Description updated (diff)
  • Status changed from Accepted to Unreviewed

#3
Updated by Daniel Pittman 4 months ago

  • Description updated (diff)
  • Status changed from Unreviewed to Closed

#4
Updated by Daniel Pittman 4 months ago

Ahem. Closed, because we are moving away from the older infrastructure to something more structured and ordered in the Faces system, rather than the older application system. That should, as it encompasses more of the code, resolve this problem fully. This ticket isn’t needed because it is too tied to the old architecture, and we have other places we track the general problem.

#5
Updated by Daniel Pittman 2 months ago

  • Target version deleted (2.7.x)

Also available in: Atom PDF