x27;puppet/util/command_line'
Puppet::Util::CommandLine.new.execute
so the ruby environment is fixed at the origin
Anyone uses ruby 1.9.3 (for example 1.9.3-p327, I know p0 is broken for
puppet), maybe through rbenv or rvm?
Thank you
--
Andrea Cappelli
--
You received this message becaus
Il 29/01/2014 19:10, Kurt Wall ha scritto:
http://docs.puppetlabs.com/guides/best_practices.html
Thank you Kurt
--
Andrea Cappelli
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiv
adopt
writing your puppet code, for example you use the :: on topscope
variables? You yse puppet-lint (or a similar tool) to check your style?
Thanks
--
Andrea Cappelli
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from
Il 17/01/2014 13:12, Jason Antman ha scritto:
On 01/16/2014 11:56 AM, Andrea Cappelli wrote:
Hi,
I'm searching through the logs of my master for the warning in the
subject, to move to Puppet3
Sometimes in the warning the manifest name isn't showed up, thereis a
reason?
Thu Jan 1
etlabs.com/guides/scope_and_puppet.html. To see the
change in behavior, use the --debug flag.
How can I easy discover where the dynamic lookup occurs in the first case?
Thank you
--
Andrea Cappelli
--
You received this message because you are subscribed to the Google Groups "Puppet
U
i,
I suppose you have to use require => Class["ssh::install"] instead of
require => Class["ssh:install"] (double ::)
HTH
--
Andrea Cappelli
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe fr