search for: hiera_array

Hi, It''s easy enough to modify, say, the "exclude" variable in /etc/yum.conf with something like: augeas { yum_exclude_kernel: context => ''/files/etc/yum.conf/main'', changes => ''set exclude kernel*'' } However, I''d like a more flexible system where I can "build" the list of excludes from

...%datacenter1 ALL=(ALL) ALL - filename: datacenter2_sudo - contents: | %datacenter2 ALL=(ALL) ALL %datacenter3 ALL=(ALL) ALL This is the closest I''ve been able to get, however, notice I''m not using ''hiera_array'', thus, only 1 level of hierarchy is written. class sudo_crap { # Errors with: # Error: Could not run: Hiera type mismatch: expected Array and got Hash #create_resources(sudo_crap::sudo_configs, hiera_debug_array(''sudoers'')) > # works for only one level o...

When using "include" to include a class Hiera helpfully performs an autolookup on the parameters of the included class. Specially-named variable names are automatically pulled from the Hiera datastore(s) and passed into the included module. This is pretty awesome. But it looks like included resources _only_ perform a hiera() lookup. If we have a hash defined in several levels of our

Hi folks, I''ve poked around the language reference, and havent found anything on this so far. I''d like to be able to force a clean early exit from a module. WITHOUT encasing the whole body of the module in an if statement. What I''m looking for: class somemodule { #no this isnt going to be a global variable I''m just using that as an example, if

Given the following hiera hash: common.yaml: --- *allowed_ips:* * "First IP": 1.2.3.4* * "Second IP": 5.6.7.8* and the module: *class iptables ($role) {* * file {/tmp/test:* * content => template(iptables/test.erb)* * }* *}* with the corresponding template test.erb: *<% role.each do |role| -%> * * code* *<% end %>* *<%

...`-- site.pp | | |-- lib | | | |-- hiera | | | | |-- backend | | | | | `-- puppet_backend.rb | | | | `-- scope.rb | | | `-- puppet | | | `-- parser | | | `-- functions | | | |-- hiera.rb | | | |-- hiera_array.rb | | | |-- hiera_hash.rb | | | `-- hiera_include.rb | | `-- spec | | |-- spec.opts | | |-- spec_helper.rb | | `-- unit | | |-- puppet_backend_spec.rb | | `-- scope_spec.rb | `-- tomcat | |-- files |...

...9;: is_puppet_master => true; } Basenode is: class basenode ( $is_puppet_master = false, $apt_host = ''repo.domain.com'' ) { ... } For the module, hiera is not explicitly used. Also, root@ll-puppet-master-vm:/usr/lib/ruby/1.8/puppet/parser/functions# ls hiera* hiera_array.rb hiera_hash.rb hiera_include.rb hiera.rb Am I missing something? Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/BN3tA57HB1AJ. To po...

Hi all, I am trying to understand how does hiera puppet backend work, so I created the following example: hiera.yaml has only: --- :backends: - puppet --- And the node: node ''testnode'' { $variable = ''kk'' $thing = hiera ("variable") notify { "note: $thing": } } I don''t want to use the yaml backend for now, just want to

...Ms to be excluded in /etc/yum.conf, then build the exclude line from all those classes that set an exclude. In my hiera hierarchy, I use %{calling_module}, but I actually modify the yum.conf exclude line from a "yum" module so of course setting yum_excludes in various classes and calling hiera_array(''yum_excludes'') is not going to work as the %{calling_module} will be "yum". Any ideas? Thanks! Gonzalo -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@goog...

Is it possible to have Hiera look at a key set for the node first, before looking at other items in the hierarchy? In particular - I''m using Puppet Dashboard and am setting keys & params for there, so I would like for any value set there for a node to be used over another item in the hiera hierachy. What value would I have to specify in the hierarchy for this, if it is possible?

Hiera was properly working in my environment. But puppet was looking at old version even when I have the latest hiera gem installed. So I could''nt use json backend. But puppet is not looking at my latest hiera gem. Not sure when went wrong here. Scenario: I have installed hiera couple of months back. So the gem was installed under /opt/puppet/lib/gems/1.8/gems/hiera-0.3.0

Dear all, This is a continuation of another thread, but I think the question diverged enough to create a new one. I have a hiera hierarchy like this: :hierarchy: - %{fqdn} - %{secundary_group} - %{primary_group} - %{productname} - all And I need to define the secondary/primary groups as facts, on the nodes. Gary has suggested me to use plugins, that they will provide the facts before

Hi, I worked with puppet (< 0.25) back in 2008/2009. We were able to deploy 200 servers from scratch and manage them. It worked fine. I''m now with a new customer and I''m pushing Puppet (and I''m also back to puppet on a side project). We''re considering Puppet 2.6 to manage RHEL/CentOS 5 or 6 hosts. I''m "upgrading myself" to Puppet