- Original Message -
> From: "Erik Dalén"
> To: "Puppet Developers"
> Cc: puppet-us...@googlegroups.com
> Sent: Thursday, May 29, 2014 4:04:01 PM
> Subject: Re: [Puppet-dev] Tracking orphaned resources
>
> There is /var/lib/puppet/state/s
There is /var/lib/puppet/state/state.yaml that records all resources ever
managed and when they were last checked & synced. However it only has the
type and title of the resources, so it might be tricky to actually find out
what they were in some cases.
I'm not aware of any tools that make good us
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
