search for: hieradata

...with Puppet 3.0 to streamline some of my module configuration... However I''m having issues using the ''*%{::clientcert}*'' variable as part of the hierarchy... Currently, my *hiera.yaml* file looks like: --- :backends: - yaml - json :yaml: :datadir: /etc/puppet/hieradata :json: :datadir: /etc/puppet/hieradata :hierarchy: - nodes/%{::clientcert} - common/%{::location} - common/%{::environment} - common/common */etc/puppet/hieradata* contains: -bash-4.1$ ls -R /etc/puppet/hieradata/ /etc/puppet/hieradata/: common nodes /etc/puppet/hieradata/common: commo...

...pec in [/usr/lib/ruby/gems/1.8/specifications/tilt-1.3.3.gemspec]: invalid date format in specification: "2011-08-25 00:00:00.000000000Z" => true *Directory structure* [root@puppet-dev puppet]# tree /etc/puppet/environments/ -d -L 2 /etc/puppet/environments/ ├── development │ ├── hieradata │ └── modules └── production ├── hieradata └── modules *Configuration file* [root@puppet-dev puppet]# cat /etc/hiera.yaml --- :hierarchy: - %{environment} - %{operatingsystem} - common :backends: - yaml :yaml: :datadir: ''/etc/puppet/environments/%{environme...

I am having a bit of difficulty implementing hiera-gpg; particularly with accomplishing the deencryption in my manifests. Can anyone either provide a simple example or point me to a good resource? I have searched alot and am still struggling. Any help would be very appreciated! Thanks! Bee -- You received this message because you are subscribed to the Google Groups "Puppet Users"

Hi Guys, I have a few questions about 3.6 directory environments, which we're looking to adopt. Currently the most pressing surrounds the integration of r10k and hiera… I believe I want to store hieradata inside the r10k repos, so that each r10k repo (I'm planning on using these to segregate different internal product stacks so that product owners can put sensitive data in their own hiera hierarchy, without the members of other products having access to the sensitive data) It seems that if I wa...

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

Hi: I work on puppet 3 and hiera, but i cannt load a yaml file on a subdir. my hiera.yaml looks like: --- :backends: - yaml - json :yaml: :datadir: /etc/puppet/hieradata :json: :datadir: /etc/puppet/hieradata :hierarchy: - "servidores/%{clientcert}" - %{::ve} - common :puppet: :datasource: data problem is on "servidores/%{clientcert}". If it is %{::clientcert} and file is on root dir ( /etc/puppet/hieradata), everithing works fine. I...

...all that information on the BackupPC server to generate proper configuration files for each node''s backups. Here''s what I have so far... $ cat /etc/puppet/hiera.yaml --- :hierarchy: - %{fqdn} - common :backends: - yaml - puppet :yaml: :datadir: ''/etc/puppet/hieradata'' :puppet: :datasource: data An example of the BackupPC information in hiera $ cat /etc/puppet/hieradata/dc-ctrl.tamu.edu.yaml --- backuppc_db_dumps: foreman: backup_dir: ''/usr/share/foreman'' mysql: backup_dir: ''/etc'' I am currently usin...

...stname ) { notify {''role::ui::notify'': message => "role::ui configured for ${::data_center}; hostname: $public_hostname", } } This is then included into the default node configuration. In my common.yaml, if I lay the file out as follows: manifests/hieradata/common.yaml ===================== --- role::ui::public_hostname: test It works fine, and the variable is available within my Puppet manifest. However, if I try and nest the YAML to make the configuration read cleaner: manifests/hieradata/common.yaml ===================== --- role: ui:...

...in Nieuwegein/base Debug: hiera(): Looking for data source Nieuwegein/management/vserver-151.dj-wasabi.nl Debug: hiera(): Found classes in Nieuwegein/management/vserver-151.dj-wasabi.nl Debug: hiera(): Looking for data source Nieuwegein/management Debug: hiera(): Data retrieved from /etc/puppet/hieradata/Nieuwegein/management.yaml is not a Hash, setting defaults Debug: hiera(): Looking for data source Nieuwegein/common Debug: hiera(): Looking for data source common Debug: hiera(): Data retrieved from /etc/puppet/hieradata/common.yaml is not a Hash, setting defaults Error: Could not find class use...

...pet. I''ve come accross hiera and installed it, and it works superbly, but how to store per-node key in hiera? This is my idea: hiera,yaml: --- :hierarchy: - ossec/%{hostname} - %{operatingsystem} - common :backends: - yaml :yaml: :datadir: ''/etc/puppet/hieradata'' And now in /etc/puppet/hieradata/ossec I have a bunch of hostname.yaml files, and all of them has something like this: --- ossec_client_key: ''blablabla'' ossec_id: ''2031'' Is this the right approach? It sure works :) -- Jakov Sosic www.srce.uni...

Hello, I''ve something strange : When I modify my hierarchy in my hiera.yaml, it can take up to several hours, for the modification to work. eg : I create a subdir in my hieradata, move all the concerned files into, modify my hiera.yaml > from : > :hierarchy: > - %{operatingsystem} > to : > :hierarchy: > - *os/*%{operatingsystem} > but the changes don''t work immediatly. -- You received this message because you are subscribed to...

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

...ignored parameters for ntp and now its not refreshing if I update the yaml at all, Im slightly lost at what I may be missing :) hiera.yaml --- :hierarchy: - %{certname} - %{environment} - global - %{environment}/common :backends: - yaml :yaml: :datadir: ''/etc/puppet/hieradata'' common.yaml system::packages::schedule: ''never'' system::yumgroups::schedule: ''never'' system::augeas: ''ntp'': context: ''/files/etc/ntp.conf'' changes: - ''set server[0] 0.vmware.pool.ntp.or...

Hi guys, i have a hiera.yaml config file like this: --- :hierarchy: - %{env}/%{tmp_module_name} - %{env}/%{tmp_module_name}.common :backends: - yaml :yaml: :datadir: ''/etc/puppet/hieradata'' I also have a test/some_module.yaml file like this: --- db: root : pass port : ''3306'' I am also using the hiera function from a template like this class.pp $::class::var=''db'' template.erb <%= scope.function_hiera...

I''m having some issues trying to track down a problem I''m having parsing a simple template, using create_resources and Hiera. Here''s my setup (abridged): ../hieradata/settings.yaml: *global:* * variables:* * env: foo* * * *appSpecific:* * serverName: someServer* ../modules/test/manifests/init.pp: *class test {* * create_resources(test::variables, hiera(''global''))* * $appcfg = hiera(''appSpecific'')* * * * define...

...rridden on a node specific basis by hiera. As an example; class profile::base { class { ''::ntp'': servers => [''a'', ''b'', ''c'', ''d''] } } node ''blah.com'' { include profile::base } hieradata/nodes/blah.com.yaml: --- ntp::servers: - 0.uk.pool.ntp.org - 1.uk.pool.ntp.org However, I''ve noticed that hiera''s behaviour seems to be that if a parameter is set like I do for the ntp::server param in the ntp class, it''s not looked up (all the other NTP params are...

Hi, I''m using Puppet 3.2.1 and heavily relying on hiera data bindings. I have the following situation: class software ( $my_content = undef, ) { file { ''/path/to/file'': content => $software::my_content, } } in hieradata/software.yaml (hiera.yaml seems ok): software::my_content: template(''mymodule/myfile.erb'') With this configuration I get /path/to/file to contain the string ''template(mymodule/myfile.erb)'' (that is, template() function isn''t evaluated). Is this a norm...

...t; $resource2_type[$resource2_name] } } And a wrapper class to use it via hiera: #basic::order_resource class basic::order_resource ($instance){ $real_instance = hiera_hash(basic::order_resource::instance) create_resources(basic::order_resource::ordering, $real_instance) } Sample yaml in hieradata: basic::order_resource::instance: foo_limits_sub: resource1_type: Limits::Limits resource1_name: foo_limits resource2_type: Service resource2_name: foo notify: true However, as I already stated, my generic define doesn''t actually work and returns the following erro...

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

...node entry. For data such as that I figure I can document the format of what the module expects from the yaml files, but if I use hiera to replace the typical "module::params", how do I include that in a published module? All the docs I''ve seen seem to show using paths for hieradata that are not specific to a module. What''s the best way to publish a module that has things like package names defined through hiera? How would someone installing such a module make the hiera yaml files distributed with the module available to hiera lookups ? Thanks - Trey -- You re...