Feature #12968
acceptance tests for re-configuration
| Status: | Accepted | Start date: | 03/05/2012 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | settings | |||
| Target version: | - | |||
| Affected Puppet version: | Branch: | |||
| Keywords: | ||||
Description
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
History
#1
Updated by Chris Price about 1 year ago
- Assignee deleted (
Chris Price)