search for: extlookup_datadir

...there is a very big downside - the inability to match the fqdn based on a regular expression.  This was brought up in a previous thread[2]. As an example, here is my existing extlookup configuration from site.pp: $hostgroup = regsubst($hostname, ''-*\d+$'', '''') $extlookup_datadir = "/etc/puppet/environments/${environment}/manifests/extdata" $extlookup_precedence = [ ''hostnames/%{fqdn}'', ''hostgroups/%{hostgroup}'', ''common'' ] This layout is quite beautiful, as it has three possible matching scenarios. 1. A CSV...

I''m trying to upgrade from 2.6.7 to to 2.7.6 and I''m running into an issue in my extlookup() calls. A lot of the variables which should be defined aren''t defined within extlookup.rb. I''ve tested 2.6.7 agent and 2.7.5 agent against the 2.6.7 master and 2.7.6 master. I adjusted extlookup.rb slightly to provide some debug output.

Anyone able to explain why "$fqdn" works and "$environment" doesn''t in: $extlookup_precedence=["%{fqdn}","%{environment}","common"] How to reproduce it: ----------------------------- - In "/etc/puppet/manifests/site.pp" : $extlookup_datadir = "/etc/puppet/manifests/extdata" $extlookup_precedence=["%{fqdn}","%{environment}","common"] - In "/etc/puppet/manifests/extdata/common.csv" extdata1,"CommonData1" extdata2,"CommonData2" - In "/etc/puppet/manifests/extdat...

...ostgroup>/<hostgroup>.yaml hiera_include( "site_classes" ) # Maintained in hostgroups/<hostgroup>/<site>/<site>.yaml hiera_include( "node_classes" ) # Maintained in hostgroups/<hostgroup>/<site>/<hostname>.yaml } $extlookup_datadir = "/etc/puppet/manifests/extdata" $extlookup_precedence = [ "%{hostname}" ] -- 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 puppet-u...

I''m new to Puppet, and I''m a software developer, not a sysadmin, so be gentle. I have puppet managing some files via templates, and one of the template variables that needs to be plugged in is a password of sorts that shouldn''t be generally available. In particular, it can''t be stored in the manifest, as that''s stored in version control, and the

Has anyone else ran into this? debug: /Stage[main]/Mcollective/File[/var/tmp/facts.yaml]/content: Executing ''diff -u /var/tmp/facts.yaml /tmp/puppet-file20121214-13448-933j3r-0'' notice: /Stage[main]/Mcollective/File[/var/tmp/facts.yaml]/content: --- /var/tmp/facts.yaml 2012-12-14 00:53:20.000000000 +0000 +++ /tmp/puppet-file20121214-13448-933j3r-0 2012-12-14