similar to: Poll for thoughts on hierifying modules and OS default differences

hello, Till now hiera-puppet was the only way I know that allowed hiera data to be loaded from inside a module. The problem with this was that it was still subject to the site specific hierarchy which means a module author had a pretty hard time to store his data in a proper way in his module thus perpetuating the use of the params classes pattern. Now that Puppet 3 is out and it''s gem

Hello, I''m running Puppet agent stand-alone on Windows. I got data-in-modules working. However, no matter what I put into the module hiera.yaml, I can only override the defaults from common.yaml by osfamily (and not, e.g., by environment). In the setup below the following command outputs: >puppet apply --binder -e "notice lookup (''my_key'')"

Hi, I am trying to use Hiera in puppet 3 and I have two nodes that both need the same configuration. In this case they are two web servers which have the same apache configuration. Rather than creating two seperate hiera files for node1.yaml and node2.yaml is there a way to group these by role (e.g. webserver.yaml)? I want to avoid duplicating the configuration if possible and keep the data

Hello, I''m trying to come up with a generic wrapper class for use with hiera so that I can have a service that is completely managed and configured via hiera and its own puppet module to be notified by Puppet of changes to a file or other resource managed by a different class/module. The example I''m using here is the management of /etc/security/limits.conf for a service account

Hi all, just installed the puppetlabs-mysql module for puppet on my Puppet server which is an Amazon Linux (based on RedHat), but I get this error when I run puppet agent --test : *err: Could not retrieve catalog from remote server: Error 400 on SERVER: Unsupported osfamily: Linux operatingsystem: Amazon, module mysql only support osfamily RedHat and Debian at

I''ve run into an odd one on one of my new RHEL 6 boxes. Puppet and Facter seem to disagree about the value of a fact. Puppet version: 2.7.9 Facter version: 1.6.4 Module: puppetlabs-apache apache::params falls through its if structure: if $::osfamily == ''redhat'' or $::operatingsystem == ''amazon'' { ... } elsif $::osfamily ==

Hi, I''m having a hard time figuring out how to make rake spec tests work correctly with hiera and puppet 3. Should I just give up for now until the various gems work with puppet 3? -- maarten -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Hi, I''m gettinng a dependency cycle when using PE 2.7, puppetlabs::mrepo, "role classes" and hiera : I''m trying to mirror RHN repos : # ROLE CLASS > class site::yum_repository{ > > $repos = hiera(''site::yum_repository::repos'') > create_resources(mrepo::repo::rhn, $repos) > } > # HIERA DEFAULTS >

Hi I am new in Puppet and i have one error when i test Postgresql module in infrastructure mode. I''m using Puppet 3.1.0 in Debian squeeze or 6.0.7 i tape the next command puppetd -t -v and this is the error info: Retrieving plugin info: Loading facts in pe_version info: Loading facts in postgres_default_version info: Loading facts in iptables info: Loading facts in puppet_vardir

I''ve written and deployed a simple Linux SSH module. But I need to modify to include support for FreeBSD and AIX. On top of that, I need to include some conditionals in there that (for example) if (/etc/file1 contains string abc) ; then install sshd-config-x & ssh-config-x elsif (/etc/file1 contains string xyz); then install sshd_config-y & ssh_config-y else install

Hi all, We''ve recently started exploring the role / profile / component module described by Craig Dunn in his blog here: http://www.craigdunn.org/2012/05/239/ and discussed on the list the other day. As I was implementing this for a profile using the apache module, I realized that I could make another refinement to our approach by using

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

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

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

Hi everyone, The hiera command line program (version 0.3.0) is currently taking around 2 seconds per invocation. This seems quite slow to me, but is probably not an issue for most users. We have a number of legacy machines that for one reason or another have not been puppetised yet, and probably won''t be anytime soon, so I have a somewhat clever script that, for each of these

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

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