The Puppet Labs Issue Tracker has Moved:

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using See the following page for information on filing tickets with JIRA:

Feature #12968

acceptance tests for re-configuration

Added by Chris Price about 4 years ago. Updated about 4 years ago.

Status:AcceptedStart date:03/05/2012
Priority:HighDue date:
Assignee:-% Done:


Target version:-
Affected Puppet version: Branch:

We've Moved!

Ticket tracking is now hosted in JIRA:


for ticket #7749, I’m working on some issues relating to simplifying the evaluation of settings / defaults. Some of this work may necessitate a change in the order that certain ruby files get evaluated.

I’ve just discovered some comments in the code that imply that we might be polling for changes to puppet.conf and allowing on-the-fly reconfiguration of the system. If that is the case, it seems critically important that we put together some acceptance tests for this functionality if they do not already exist. Without them we don’t know whether things are currently working as expected (or probably even what the expected behavior is)…

and we definitely won’t know if cleanup work w/rt settings / defaults will affect this functionality.

Related issues

Related to Puppet - Refactor #7749: Bootstrapping Puppet in Ruby code has nasty scope cycles... Closed 06/01/2011


#1 Updated by Chris Price about 4 years ago

  • Assignee deleted (Chris Price)

Also available in: Atom PDF