nyone have an opinion as to why this is a terrible idea? I ask
because I have submitted a pull request for the change prior to reading the
very informative page about contributing to puppetlabs modules and would
value any community feedback on my approach.
Regards,
Nic
--
You received t
thanks! this is what i suspected. but, my core issue then, it would seem,
is that the node_aws cloud provisioner does not run the puppet agent in
sudo.
i think this is the case, because when i provision a new agent via node_aws
and provide a --certname, the autosigning process ignores it and uses
r to svn:ignore. Then git could
be used to pull updates from GitHub, where most of the puppet forge modules
are developed.
--
Nic
On Friday, 12 April 2013 05:55:52 UTC-7, Ygor wrote:
>
> I use Subversion to maintain the $confdir of my puppet-masters and I just
> discovered that when o
I'm evaluating puppet to see if it can work in our environment and I have
to admit the the learning cure with the puppet "terms" are giving me
issues. I keep reading documentation into circles. I'm familiar with
python, bash scripting, and use munki in my labs, but I'm stilling trying
to unders