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 module Foo, resources managed by Foo are present in A but "orphaned". This is a lurking gotcha; and it can lead to subtle problems. Is there any tool that helps here, for example keeping a manifest of all resources ever managed by this puppet install? If not, I will probably try build that into ppg. Is there a way to ask puppet for a fuller, more explicit report of all resources tracked during a run? Thanks, m -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CACPiFCLhd34r%3DNjC91kFOq97VGbUpbdWmYC1Z75CgirmO%2Btsug%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
