Hi,
The situation ;
Whenever I bring up a vagrant box, I do a puppet run against my puppet
master to configure some common things I need.
And I want to avoid the remove/new request and sign cycle after a
vagrant destroy.
This can be done using following vagrant config :
vm_config.vm.pro
Because it is in your puppet.conf :
external_nodes = /etc/puppet/node.rb
more info about ENC : http://docs.puppetlabs.com/guides/external_nodes.html
On 02/27/2014 07:29 PM, mjack...@broadsoft.com wrote:
Hi,
I uninstalled foreman. why would node.rb be utilized?
Regards,
On Wednesday, Febr
Hi,
IMO, I think it is a good thing not to develop your modules under root
account.
So for me this is more a feature than a problem.
Grts
Johan
On 02/26/2014 07:58 AM, Stephen Wallace wrote:
Peter,
When I ran the puppet module generate as non-rootit worked like a
charm! Maybe some of
it is always handy to show your command.
Assuming you did a a pupept apply, add the --modulepath to the command.
puppet apply --modulepath=/tmp/vagrant-puppet-1/modules-0/
/tmp/vagrant-puppet-1/modules-0/ntp/tests/init.pp
puppet knows now where to find the other classes.
HTH
grts
jo
On 02
Hi Helen,
"INSTALLDIR=${::agenthome}\jre"
HTH
Jo
should do the trick
On 02/25/2014 10:52 AM, Helen Paterson wrote:
Hi,
What is the syntax for install_options containing a variable ?
This code below works fine,but i'd like to remove D:\BuildAgent\jre'
and replace it with ${::javahome}, what
