Working on another way to identify dead code if anyone would like to kick the tires on it: klabsystems/dead_code_detector · Identify unused classes, types, functions, templates, and static files across your Puppet infrastructure · Puppet Forge Please open an issue here: Issues · klab-systems/dead_code_detector if you run into any major issues with it and I can review accordingly. Thanks for taking a look!

How is this spiritually different from puppet-ghostbuster?

I was targeting a different user experience from ghostbuster and also having no underlying gem dependency issues. example: Starting in ghostbuster v2.0.0 the underlying gem dependency was switched to openvox making it so you cannot run it on your puppet primary. This solution works the same for Puppet Core / Open Vox / PE it's simply run task / plan against your primary.