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 #14128

optionally clean exported resources for a host during puppet run

Added by Reinoud van Leeuwen about 4 years ago. Updated over 3 years ago.

Status:Needs DecisionStart date:04/23/2012
Priority:NormalDue date:
Assignee:Deepak Giridharagopal% Done:


Target version:-
Affected Puppet version: Branch:

We've Moved!

Ticket tracking is now hosted in JIRA:


Problem: When the configuration of a host changes (classes might be removed), old exported resources stay in the storeconfig database.

Businesscase: Suppose we have implemented a central backupserver. backup clients export resources, and the central backupserver collects them to generate a config file that contains all hosts to backup. Once in a while we need to remove a client from the backupserver. removing the “class { ‘centralbackupservice::client:; }” statement from the nodefile will not help, since the exported resources will stay in the database and will keep being collected by the server. Similar cases can be described with changing nagios services which behave in a similar nature.

Solution: a configurable switch that does a “delete all exported resources for this host” during the puppetrun on the client. This should be encapsulated in a single database transaction that puts all exported resources back into the storeconfig database to make sure that a concurrent puppettun on the servermachine will not request missing exported resources. The configuration can be done serverside near the storeconfig configuration, to make sure that the current behaviour will not change for installations that depend on it.


#1 Updated by Anonymous about 4 years ago

  • Status changed from Unreviewed to Needs Decision
  • Assignee set to Deepak Giridharagopal

Can you take a look at this, please.

Also available in: Atom PDF