The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:
Ability to mark resources as "under maintenance"
|Affected Puppet version:||0.25.0||Branch:|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
WHAT WE WANT:
Need ability to denote certain resources as “under maintenance” where puppet will not apply those resources during a catalog run (noop or otherwise).
ralsh should be able to integrate with the client’s catalog, so admin have the ability to introspect/modify/etc. local resources and/or mark resources as “under maintenance”.
Have a separate catalog stored on the client, same format we’d serialize normal catalog, that exclusively contains resources in “maintenance mode”.
puppet’s Transaction object will read in both catalogs, the main one and the maintenance one, and it will know not to evaluate resources marked as “maintenance”.
Modify puppet’s Report objects to include information on how many resources are in maintenance mode.
We should also modify the —detailed-exitcodes to include exit status for maintenance resources (I guess?).
#1 Updated by Luke Kanies almost 6 years ago
- Category set to RAL
- Status changed from Unreviewed to Accepted
- Keywords set to puppetcamp
This requires a bit of plumbing on the client — at the least, we need to be confident in our state file or whatever location we use for storing the maintenance state. It also requires integration on both puppetd and ralsh.