You could build a scheme after the following fashion: Have Puppet deploy credentials for your central git repository on each agent Use the vcsrepo type to allow Puppet to maintain a clone of the repo on each agent with the desired revision Have the config file resources use local sources....
ruby,templates,puppet,theforeman
I found the answer, <% key = @nodes.keys[0] -%> <%= key %> IPaddr2::<%= @nodes[key]['ip'] %>/<%= @nodes[key]['cidr'] %>/<%= @nodes[key]['interface'] %> Cheers...
I have the same setup and same result. Just did a fresh install of Foreman 1.6 without this problem. The Foreman_smartproxy register.pp has not changed between 1.6 and 1.7, but apparently something has. Thanks to Dominic on irc channel #theforman, the solution seems to be a change in the settings:...
Your conclusions are about right. But the params class pattern is independent of your scheme of node level configuration. It might be possible to tie Hiera into it more tightly, but here is what you generally want to do: Define default values in the params class. Defaults might depend on...
hash,puppet,collectd,theforeman
When putting hash data into a Foreman smart class parameter (or smart variable), you need to do two things to get it passed to Puppet correctly: Set the data type on the parameter to Hash, JSON or YAML Use JSON or YAML to represent the data The first will ensure...