On 4/3/14, 10:23 AM, Sven Sporer wrote:
> Thanks Dan, I didn't know about puppet-catallog-diff. I'm already using
> rspec-puppet to test the module logic, and extensively use VMs to test
> the bootstrap of new systems. I don't fear that I will introduce bugs in
> my modules.
>
> The issue I had in
Thanks Dan, I didn't know about puppet-catallog-diff. I'm already using
rspec-puppet to test the module logic, and extensively use VMs to test the
bootstrap of new systems. I don't fear that I will introduce bugs in my
modules.
The issue I had in mind is more of an issue with managing your modu
Hi,
A couple of things that I have tried before.
1. If the intention is to perform a refactor where the code changes are
large, but the expected changes to the catalog are small, I would recommend
looking at:
- https://github.com/ripienaar/puppet-catalog-diff
Depending on what versions of Pup
Hi,
I'm wondering if there's an established way on how to write and improve
modules with potentially system-breaking or incompatible changes. One
example are changes in the filesystem layout, or simply the change of an OS
user's homedir (usermod fails because of running processes).
Of course,
