similar to: Simple hiera-puppet usage

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

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

Hey there, I''m new to hiera and I'' m looking to configure it to use multiple environments. I''m able to query hiera keys from using the hiera CLI, however my clients seem to be having problems identifying the look up variables. *On the puppet master, CLI query* [root@puppet-dev puppet]# hiera -a sshpackages environment=development ["openssh",

Dear puppetteers, I am having a philosophical question about parametrized classes. When building modules, one wants to be as flexible as possible, to try to target as many puppet flavors as possible. This is our target: - Foreman users, using foreman as an ENC with smart variables (or potentially any other ENC, but I would say this is the most widespread one). - Pure Puppet''s site.pp

my data is getting unwieldy . . . any advice on migrating to hiera? Thanks! -- 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. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at

Hi, I''ve just run into a small glitch with Hiera. I have a YAML file that has a definition like this: puppet_agent_splay: false but the run fails because of "err: Could not find data item puppet_agent_splay in any Hiera data file and no default supplied at /puppet/modules/puppet/manifests/agent/config.pp:6 on node slave1.local" Digging into this it turns out that lookup in

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

Dear all, I have observed a behavior that doesn''t seem (to me) to match the documentation. Specially, about tagging, the doc says: " Automatic Tagging All language statements enclosed in a node, define or class structure (read more about puppet control structures [[Language Tutorial]] ) will automatically be tagged with the name of that statement. These automatically- applied

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,

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

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

Dear all, We have a few reasons to have various PuppetDBs (and Masters, one per cluster) in our datacenter and, eventually, there may be a need to share *only* a few exported resources between clusters, like a few ssh-keys or nagios tests. Is there a mechanism to pull and push some exported resources from one PuppetDB to another? I guess this could be done with the API, but has anybody tried it,

Hi all, I''m interested pushing my user list out of my users manifest and into Hiera. Unfortunately I haven''t been able to get it to work the way I thought it would. The error suggests that perhaps create_resources cannot create virtual resources, but the docs I''ve read so far don''t address it. The class (in init.pp): class users { $system_users =

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, If I have understood it correctly, puppet 3.0.0 will include / require hiera. In order to add support for hiera directly in Geppetto I downloaded the puppet 3.0.0rc tarball expecting to find the puppet-hiera functions, but they where not there. What is the expected packaging going to be when 3.0.0 is released? Where should I expect the hiera "parser functions" to be located?

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

Hello lovelies, Our team is deliberating a few different options for the hierification of our modules; and wanted to poll the collective genius before making our decision. As we all know, there are certain attributes of a package which are, by default, consistent on an OS... say, the name of a package..... class foobar { include foobar::params $package = $foobar::params::package Package

Just started a rollout of centos 6.x across our Puppet deployment (100-odd servers). what fact would people suggest I use to distinguish 5.x from 6.x (quite a lot of subsystems are different between major releases)? lsb* facts don''t seem to be present on centos 6 - is this an EPEL bug, or have they just been removed in Facter? Thanks! -- You received this message because you are

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