similar to: Converting to heira format issue

Hi all! I''m trying to setup a puppet module for sudo that will write multiple files with separate data for each file, all dependent on the hiera hierarchy. Here''s the relevant portion of my hiera.yaml: > :hierarchy: > > - "datacenter/app/role/node/%{::clientcert}" > > - "datacenter/app/role/%{::server_role}" > > -

Hi everyone, I currently have a giant file with default variables I use in a lot of my modules and I override those at the node level if I need to. I thought I would give porting that data into a hiera setup. I worked out how to specify my data sources and started to make a go at moving some of my variables in the default data file. I thought heira would be smart and set a variable to undef if

I am using puppet 2.6.11 and want to pass parameter for implementing sudo for mulitple users. So here is my simple code, which I would like to pass to hiera to specify user name lookup. Appreciate any help, thanks in advance. class sudo( $name) { #Class:: sudo # # package { "sudo": ensure => present, } file { "/etc/sudoers": owner => root, group => root,

Hello I am setting up servers with a puppetmaster and various nodes, all running Debian Wheezy with the Puppet 3 packages from Puppetlabs. The Puppetmaster is configured with Passenger and Apache. I am trying to use hiera-gpg to encrypt passwords, I have it installed and have created a key as described here: http://www.craigdunn.org/2011/10/secret-variables-in-puppet-with-hiera-and-gpg/ On

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

Hello all, I don''t know if I have hit a strange bug or it''s just an incorrect interpretation about how parameter autoloading works... Today I have been searching, analysing and about to hit my head against a wall trying to figure out why a call to hiera_hash was not merging data from top level among different hierarchies. The problem was that I was trying to do something

Hello, I have number of classes that deal with user management and I''ve run into a snag with needing to extend/modify either the user or group types. I''m using theforeman as an ENC. The class structure I have is something like the following. users::common users::dev users::prod etc... users::{dev, prod} do not use inheritance. Almost all node include users::common.

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

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

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, Before I begin, my environment consists of a standard master/client config with the exception that all my clients run under a non-root user. I have to use non-root so I can''t simply restart under root to fix the problem. Master -> 3.1.1 Client -> 2.7.17 using mostly the hiera() function in my classes. problem: I have run into an issue today where my custom fact is not

What is the right path for ruby gems on puppet master. 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 /opt/puppet/lib/gems/1.8/gems/hiera-puppet-0.3.0 Later when I updated to new version of hiera then it installed (via gem install) under /opt/puppet/lib/gems/1.8/gems/hiera-1.1.1

Hi all, I''m trying to work with hiera database in puppet and i''m having problems using %{variables} because they don''t get the values and i don''t know why. file hiera.yaml: cat hiera.yaml --- :backends: - yaml - puppet :hierarchy:- nodes/%{domain}/%{hostname} - os/%{operatingsystem}/%{operatingsystemrelease} -

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

I''m not sure at all what''s going on here, but I''ve spent a lot of time reading over the puppet hiera docs and setting everything up, but when I run puppet agent it just seems to ignore the hiera setup completely. Both the puppet master and agent nodes have exactly the same versions of puppet and hiera (installed via the official puppet APT repository). I''ve

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

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 │ └──