[PUP-1042] Change --write-catalog-summary option into a config setting - Puppet Tickets

XML

Word

Printable

Epic Link:
Puppet Settings
Team:
Coremunity
Story Points:
1
Sprint:
Week 2014-1-22 to 2014-1-29, Week 2014-1-29 to 2014-2-05, Week 2014-2-5 to 2014-2-12, Week 2014-2-19 to 2014-2-26, Week 2014-2-26 to 2014-3-5, Coremunity Kanban

Release Notes:
Enhancement
Release Notes Summary:

Hide
Adds a "write_catalog_summary" setting to control whether the "resources.txt" and "classes.txt" files are written to disk after applying a catalog. By default, "puppet agent" and "puppet apply" behave the same as before. The latter will write those files by default, but "puppet apply" will not.

Show
Adds a "write_catalog_summary" setting to control whether the "resources.txt" and "classes.txt" files are written to disk after applying a catalog. By default, "puppet agent" and "puppet apply" behave the same as before. The latter will write those files by default, but "puppet apply" will not.

Overview #
The classes.txt file is only written when running Puppet in the agent run mode.

It would be useful for integration with MCollective filtering if this
file were also written when running Puppet the stand alone apply run
mode.

# The file in which puppet agent stores a list of the classes

# associated with the retrieved configuration.  Can be loaded in

# the separate `puppet` executable using the `--loadclasses`

# option.

# The default value is '$statedir/classes.txt'.

classfile = /var/lib/puppet/state/classes.txt

This would be useful with MCollective's configuration setting of:

classesfile = /var/lib/puppet/state/classes.txt

At least one community member has requested this feature. (See comments below).

This ticket is important for mcollective integration with "puppet apply."

relates to

PUP-7580 Exec resource exposing Sensitive data

clones

(#7917) Puppet apply runmode should write classes.txt file