similar to: Puppet module change management - best practices?

I am using puppet 2.7.14 on Ubuntu 10.04 LTS. I have the following gems: *** LOCAL GEMS *** diff-lcs (1.1.3) hiera (0.3.0) hiera-puppet (0.3.0) metaclass (0.0.1) mocha (0.12.1) puppet-lint (0.1.13) puppetlabs_spec_helper (0.2.0) rake (0.9.2.2) rspec (2.11.0) rspec-core (2.11.1) rspec-expectations (2.11.2) rspec-mocks (2.11.1) rspec-puppet (0.1.3) When I run "rake help" I get the

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

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

I''ve begun moving some of my modules the using hiera lookups in place of parameters being defined in a host''s node entry. For data such as that I figure I can document the format of what the module expects from the yaml files, but if I use hiera to replace the typical "module::params", how do I include that in a published module? All the docs I''ve seen

We''re running puppet 2.7.11 and facter 1.6.1. We''re at a point where we need to start having some custom facts for our environment but we''re not sure the best way to go around it, so I''m looking for feedback from the community. I''ve setup custom facts with facter now and have successfully polled these and also proven that the puppet clients have

This is the situation I have: All my hosts are the* same OS.* All my host are in the* same puppet environment,* so I cannot use %{environment} I have a module that sets all the *basic* functionality for the OS, resolution, authentication, security, packages, etc I have a module for each application hosted. At the moment all the ''data'' is in Puppet, mostly in parametrised

Hi Puppet Users, For some bizzare reason I am unable to use hiera-puppet with a parameterised class. The output is: ---------------------------- root@hiera hieratest/manifests# puppet apply -e "include hieratest" Error: undefined method `catalog'' for #<Hash:0xb6c53d00> at line 1 on node hiera.localdomain Wrapped exception: undefined method `catalog'' for

Hi, I''m trying to use standard hiera on puppet (gentoo). I simply did # gem install hiera Then setup /etc/hiera.yaml When i call the hiera() function in puppet i get "Error 400 on SERVER: Unknown function hiera at /data/puppet/manifests/ site.pp:27" Is there a step that I''m missing? BTW. standalone hiera works fine. -- You received this message because you

Hiera-Puppet 1.0.0rc1 is a feature release candidate designed to accompany Puppet 3.0 and Hiera 1.0. It includes Puppet functions for hiera and also the puppet backend for hiera lookups. Downloads are available: * Source http://downloads.puppetlabs.com/hiera/hiera-puppet-1.0.0rc1.tar.gz * Apt and yum development repositories * Apple package

I have a module located at /etc/puppet/environments/test/modules/ruby. I n this I have a manifests folder with two .pp files - init.pp and gemInstall.pp. In one of my node def files I have: include ruby ruby::gemInstall { ''someGem-version.gem'': path => ''/path/to/agent/local/gem/repo'', } ruby::gemInstall is a define, and it has some logic to get around

I just installed puppet 3 (3.0.0-0.1rc3puppetlabs1) on a 32bit Ubuntu 12.04 ''server'' VM. I used the packages for the install. I then copied over my existing modules and manifests from my production 2.7.x puppet master, and also my hiera.yaml and hieradata/*. When I run puppet agent --test I get the following: Error: Puppet::Parser::AST::Resource failed with error

Hello, just upgraded Hiera from ver. 1.2.1 to 1.3.0 and broke our puppet environment. :) It seems that there are sizeable changes related to variable interpolation Here is an error during Puppet run: Error: Puppet::Parser::AST::Resource failed with error Hiera::InterpolationLoop: Detected in [::environment] at /home/ubuntu/environments/project_dev/manifests/site.pp:35 on node

Hi, if possible can someone post a working example please ? I am using hiera => puppet => augeas. cat myserver.yaml --- myserver: "Birthday": ''1'' "Debug": ''5'' The no. of settings will change, so i would like to use a hash here. The hiera lookup works already: >hiera -c /etc/puppet/hiera.yaml -h myserver

Hi All, I am using Vagrant to provision a box (CentOS 6.x) with puppet provisioner. The box is built by using veewee, with ruby 1.8.7 and puppet 3.2 iinstalled, and the vagrant environment layout is, . ├── Gemfile ├── Gemfile.lock ├── Rakefile ├── Vagrantfile ├── definitions │ └── centos-6.3.minimal ├── hiera │ └── data ├── iso │ ├── CentOS-6.3-x86_64-minimal.iso │ └──

All, I have found very few references to this error so I''m guessing I must be doing something wrong. I have just started using hiera and am trying to use it in the simplest way possible, I have a class that looks like this: class app_users2($compresslogs = hiera(''compresslogs'')) {

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''m looking to implement a hiera backend for our Puppet installation, as we routinely deploy systems that are of varying hardware, OS, and which may have multiple roles they fill. I''ve figured out, I think, how to handle the OS question through facter, but implementing server roles isn''t quite so clear. I want to maintain that information on the server, not on the

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:

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:

Hi there, I''m running into an problem which I can resolve. It is bugging me for couple of days now. Goal: CentOS 6.4 freshly installed incl puppet 3.2.3 and I want to install puppet master, puppetdb, mod_passenger & apache with "puppet apply". So when this is complete, I should have an puppet master server running so I can create new hosts etc. So this is the command