similar to: Lookup and scoping of hiera data from erb templates

I''m having some issues trying to track down a problem I''m having parsing a simple template, using create_resources and Hiera. Here''s my setup (abridged): ../hieradata/settings.yaml: *global:* * variables:* * env: foo* * * *appSpecific:* * serverName: someServer* ../modules/test/manifests/init.pp: *class test {* * create_resources(test::variables,

I want to have a parametrized class with lookup from params.pp but I keep getting into problems. init.pp: class foo ( $bar = $foo::params::bar, $foofoo = $foo::params::foofoo ) inherits foo::params { file {''/tmp/foobar'': content => template("foo/foobar.erb"), } } params: class foo::params { $bar = true if $foo::bar { $foobar =

Hi, I have stupid situation that I may workaround but I think there is an elegant way to deal with. Still I need the community help. In some class X I have: $control = { dev => { id => 7, name => ''GG'' }, prod => { id => 1, name => ''Info'' } } In some other class, which I apply to a node I have defined file from a

Hi guys, I''m trying to do the following in my template: location <%= location %> { proxy_pass <%= proxy %>; <% if scope.lookupvar(''nginx::resource::location::proxy_header'') then scope.lookupvar(''nginx::resource::location::proxy_header'').each do |header| %> proxy_set_header <%= header %> <% end

Hi, I''m using Puppet 3.2.1 and heavily relying on hiera data bindings. I have the following situation: class software ( $my_content = undef, ) { file { ''/path/to/file'': content => $software::my_content, } } in hieradata/software.yaml (hiera.yaml seems ok): software::my_content: template(''mymodule/myfile.erb'') With this configuration I

Hi, I''m trying to reconcile the advice in the Puppet 3 class doc with our current use of Hiera. We currently retrieve variables from Hiera in one big collection while the Puppet 3 doc seems to indicate storing variables without the collection. For example, we have a module to manage a log indexer. In its init.pp it says: class log_indexer( $log_indexer_conf =

I''ve begun using Hiera in combination with Foreman, primarily storing data that is best left in Array/Hash form. I''d like to be able to have a module, in this case BackupPC, query all the Hiera data for each node where the backup directories/databases are stored. Then use all that information on the BackupPC server to generate proper configuration files for each

Hello, Is there an easy way to test hiera lookup for a node? A node is not getting the value I expect from Hiera and I want a way to test this. I noticed that `hiera` has an option called `-i` to use the Puppet inventory service. With the latest (RC4 I believe) of Hiera I''m getting the following when I try to use that though: Puppet inventory service lookup failed: NoMethodError:

Hiera 1.0.0rc3 is a feature release candidate designed to accompany Puppet 3.0. Changes to Hiera since 1.0.0rc2 were mainly to ease packaging and improve testing. Downloads are available: * Source http://downloads.puppetlabs.com/hiera/hiera-1.0.0rc3.tar.gz It includes contributions from the following people: Kelsey Hightower and Matthaus Litteken See the Verifying Puppet Download section at:

I''m running Puppet v2.7.14. I have a puppet master server with Hiera and it works great. I also want to be able to apply my manifests locally on a node. I have installed Hiera on my node and I can verify using the Hiera command line application that values can be looked up: user@tag5-4-qa-sjc:~$ hiera corp_puppet_server region=northamerica datacenter=sjc environment=qa --debug DEBUG:

This may be a dumb question, but here goes So I''m running on Puppet 3.1.1 on RHEL5, and i''ve been using Hiera since 2.5/2.6 ish and it''s been great!! I was reading up on Automatic Parameter Lookups and would love to use it for my modules. But I can''t seem to ever get Hiera/Puppet to load the value i''ve set in my yaml files. I feel like I must be

Hey all, I''ve been messing around with the hiera-foreman backend to see if it would let me migrate to hiera and use foreman and an ENC. https://github.com/torrancew/hiera-foreman It works by querying each node''s yaml file from foreman. Currently this code works when called from the hiera command line with the -m (mcollective option). It uses the mcollective facts to pull

Hi guys, i have a hiera.yaml config file like this: --- :hierarchy: - %{env}/%{tmp_module_name} - %{env}/%{tmp_module_name}.common :backends: - yaml :yaml: :datadir: ''/etc/puppet/hieradata'' I also have a test/some_module.yaml file like this: --- db: root : pass port : ''3306'' I am also using the hiera function

In addition to hiera looking at files based on environment and node role etc, I''d like to be able to specify a file name based on function. Ie break keys into files by function. Is there a way to do this? Doug -- 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@googlegroups.com.

So something doesn''t look right for me when running puppet apply -e ''include ...'' for looking heria via facter fact. I have hiera configure as this, :backends: - yaml :hierarchy: - common - ''%{env_name}'' :yaml: :datadir: /var/lib/hiera/data and, a file envXX.yaml store in the datadir, and I can run *hiera xyz

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 %>* *<%

All- I''m using puppet 2.7.14. I''ve reviewed http://docs.puppetlabs.com/puppet/2.7/reference/modules_fundamentals.html but it doesn''t seem to cover what I''m attempting. Consider a module layout like this: $ tree mymodule mymodule |-- Modulefile |-- README |-- manifests | |-- init.pp | |-- special_type | | `-- prereqs.pp | `-- special_type.pp

Hiera 1.1.2-rc2 is a release candidate in the 1.x series with bug fixes. Downloads are available at: * Source: https://downloads.puppetlabs.com/hiera/hiera-1.1.2-rc2.tar.gz RPMs are available at https://yum.puppetlabs.com/el or /fedora Rubygem available at http://rubygems.org/gems/hiera or by using the --pre option to gem install. Debs are available at https://apt.puppetlabs.com Mac package

Hi, This follows on a bit from the previous thread ''trouble with hiera and puppet defines'' [1] Up to now I''ve had a large file of virtual resources and then enabled them on demand on various services. The very standard. @metric{''1234: one => 1 two => [1,2] } @metric{''abcd'': one => a, two => [b,c] } and

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