similar to: early clean exit from module?

I have these three modules with the following structure: |-- modules | |-- create_resources | | |-- LICENSE | | |-- Modulefile | | |-- README | | |-- lib | | | `-- puppet | | | `-- parser | | | `-- functions | | | `-- create_resources.rb | | |-- spec | | | |-- spec.opts | | | |-- spec_helper.rb | | | `-- unit

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

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

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

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,

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

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

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 All, I''ve been trying to use Hiera for node classification, my sit.pp is simple: node default { hiera_include("classes") } which has been working well with simple class definitions like: user@host$ cat testagent.yaml 2012-06-18 14:55:48 jon pts/13 --- classes: - motd Is anyone doing this in production? I''ve seen a little about this on line but it

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

Hi Folks, Like to get some advice on module organization. I have a system that has a few different components. One or more components can be installed on a host. The hosts also have a "type" dimension. This "type" dimension could (should) ideally be used to configure the system (fill in a bunch of variables). Problem is, I''m not sure how the best way to do

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

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

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?

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

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

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

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

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

Hello, I work for the CHTC (Center for High Throughput Computing) at the University of Wisconsin, Madison. We utilize puppet for most of our configuration management. Currently we have a web application that performs the tasks of user account management. When a new user is registered with the application, the application does some very limited parsing of a puppet manifest that has