On 2014-29-05 15:58, Martin Langhoff wrote:
As the complexity of our $workplace puppet configuration grows, I am
increasingly worried that puppet gives us very limited visibility over
resources it no longer manages.
In practical terms: if I mess up my class include/require/inherit
structure so t
Not that I've heard of such a tool, but if you archived catalogs somewhere you
could compare the lists of resources over time. Or you could turn on catalog
hash debugging to grab the current/previous catalog for the same technique:
http://docs.puppetlabs.com/puppetdb/latest/trouble_low_catalog_d
On 2014-05-29 15:58, Martin Langhoff wrote:
As the complexity of our $workplace puppet configuration grows, I am
increasingly worried that puppet gives us very limited visibility over
resources it no longer manages.
In practical terms: if I mess up my class include/require/inherit
structure so t
As the complexity of our $workplace puppet configuration grows, I am
increasingly worried that puppet gives us very limited visibility over
resources it no longer manages.
In practical terms: if I mess up my class include/require/inherit structure
so that a node A no longer indirectly includes mod
