similar to: hiera puppet augeas and hash keys ?

Howdy: I need some help please to get hiera configuration data derived from YAML, thru puppet. I have studied Internet search results and puppet documentation on create_resources and custom defines but need a little help along. I can print out the YAML from variables, arrays, and, finally, hashes too from a puppet manifest. One thing that is stumping me is how to access from the custom define

Hi, This follows on a bit from the previous thread ''trouble with hiera and puppet defines'' [1] Up to now I''ve had a large file of virtual resources and then enabled them on demand on various services. The very standard. @metric{''1234: one => 1 two => [1,2] } @metric{''abcd'': one => a, two => [b,c] } and

I am trying to use the same hiera hash to create the mount point and mounts. (Would be nice if mount could create the mount points using 3.1.1) My plan was to define create_mount_points and use create_resources with the same hash, and just though away what I dont use.... maybe there is a better means? Here is the mount class: class fstab::mounts ( $config = undef ) { $defaults = {

Hi folks, Is there a way to test the result of a hiera_hash() lookup in a manifest? I am trying to use hiera to do most of my configuration, like this for example: mysql::grants: ''user1@localhost'': privileges: - select_priv ''user2@localhost'': privileges: - select_priv - insert_priv - lock_tables_priv I have a wrapper

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

In a posting a few days ago was this hiera.yaml source listing: --------------------------------- :backends: - json :hierarchy: - %{fqdn} - %{lmax_role}_role - %{lmax_env}_server - %{pop}.tradefair - common :json: :datadir: - /etc/puppet/private/ - /etc/puppet/environments/%{environment}/hiera_data_store/ -

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

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

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

I''m trying to use create_resources to create a series of files with semi-custom content based on a template. This is what I have: foo.conf.erb: Name "<%= name %>" WorkingDir "<%= working_dir %>" ... a bunch of static entries YAML: configs: config1: Name: app1 WorkingDir: /var/app1 config2: Name: app2 WorkingDir: /var/app2

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

Hi, I have a problem with running puppet with hiera based data. I am trying to cleanup user accounts on a range of servers (to have the same uid/gid). When I create existing account but with different uid/gid it doesn''t change files group ownership so I need to run a script which cleanups after cleanup ;-) I use the following code: --- :backends: - yaml :hierarchy: -

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

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

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

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