Two things that I've come across that help this situation:
- for new modules, rspec tests
- for existing modules, https://github.com/ripienaar/puppet-catalog-diff -
I generate a catalog with the new and old branch, then diff them
On Fri, Aug 22, 2014 at 9:34 AM, Martin Langhoff
wrote:
> For con
For context... Our puppet setup is complex, with many behaviors controlled
by facter facts, in part controlled by a .INI file that support personnel
can edit. We manage thousands of VMs.
So unit tests are interesting but offer very limited coverage. Tracking
orphans on live nodes is much more comp
On 8/21/14 5:45 PM, Manuel Quiñones wrote:
> Hello,
>
> I'm working on a utility script to track orphaned resources. With
> orphans I mean: resources that were previously managed by Puppet, but
> they no longer are. I want to track those while I do a refactor in my
> manifests.
>
> Here is the
Hello,
I'm working on a utility script to track orphaned resources. With orphans
I mean: resources that were previously managed by Puppet, but they no
longer are. I want to track those while I do a refactor in my manifests.
Here is the script I wrote:
https://gist.github.com/manuq/eec269ce7b
