Hello Jeremy,
This is perfect, so long as we can stay in the loop for a migration plan we can
have lenient time frames for when this needs to be resolved. Obviously, the
sooner the better in terms of our environment, but we have room to wiggle to
ensure a well thought out plan can be
My tool of choice is vagrant - it's super easy to create a Vagrantfile,
write a quick shell script that idempotently installs any required puppet
modules, and then run puppet itself. An older example is the
puppet-storyboard module: git checkout, vagrant up, and you're off to the
races.
(sorry, mail client failure)
On Tue, Aug 30, 2016 at 4:59 PM, Joshua Hesketh
wrote:
>
>
> On Fri, Aug 26, 2016 at 1:31 AM, Simon McCartney
> wrote:
>>
>>
>>
>>
> However, I'm not sure Vagrant provides a good solution for testing puppet
>> modules
On Fri, Aug 26, 2016 at 1:31 AM, Simon McCartney wrote:
>
>
>
>
However, I'm not sure Vagrant provides a good solution for testing puppet
> modules in isolation (I think it's great for the
> system-config/project-config scenario, where you want to see how applying
> the full