similar to: Split Manifest Across Multiple Lines?

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"

Hi, I''m having a problem with extlookup not respecting the ''certname'' parameter[1].  When executing a puppet run with either the --certname or --fqdn parameters, it ends up using the specified SSL certificate and gets the correct node definition applied from the puppetmaster.  However, it still retrieves extlookup data using the node''s actual FQDN, not the one

Hmmm.... So I was just trying the extlookup function that comes with puppet 2.6.1. It now lets you do this: $version = extlookup("rsyslog_version", "present", "packages") which, according to the documentation: # This will look for a version configured in packages.csv and then in the rest as configured # by $extlookup_precedence if it''s not found anywhere

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.

Running puppet 2.6.11 opensource on Red Hat 5.6 client. I cannot explain this logically but I have a directory structure like so: /etc/puppet/manifests/hiera/hostgroups/ with directories for each of my application areas like so: *clickz core devel dns icross iswap itch puppet test ubuntu* *What is weird is that if I put anything under the directory named "core", the ext

So I''m having some problems with some of my manifests that I''ve been using for a while and I''m not entirely certain what''s going on. What appears to be happening is that puppet when it runs can''t see the value for one of the default facter facts (domain). I''m not real certain that this is the actual problem I think this is just how

On Fri, May 27, 2011 at 1:08 PM, R.I.Pienaar <rip@devco.net> wrote: > And for what its worth this afternoon just to see how hard it is > and to again ask to myself ''wtf has no-one done this yet?'' and also > ''wtf are people at Puppet Labs reinventing this wheel?'' I wrote > a new extlookup that has pluggable backends. > The bit about

I''ve got this: file { ''/opt/sugarsync/tomcat/tomcat-home/current'': ensure => "tomcat-$config[''tomcat_version_server'']"; where $config[''tomcat_version_server''] was set with extlookup (the yaml one), by loading: --- tomcat_config: tomcat_version_server: 6.0.20-1 tomcat_version_libs: 1.0-1

--- MANIFEST | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/MANIFEST b/MANIFEST index 13897af..3489ff1 100644 --- a/MANIFEST +++ b/MANIFEST @@ -18,6 +18,7 @@ MANIFEST This list of files MANIFEST.SKIP META.yml po/es.po +po/fr.po po/it.po po/Makefile po/PACKAGE -- 1.6.5.2

On Thursday, 29 September 2016 14:59:14 CEST Tomáš Golembiovský wrote: > The regular expression for parsing the manifest line was wrong. There is > a mandatory space between '=' and the hash. > > Another problem was that only the first line of the manifest file was > actually processed. Can you please provide an example of manifest file with more than one line? A real-life

The regular expression for parsing the manifest line was wrong. There is a mandatory space between '=' and the hash. Another problem was that only the first line of the manifest file was actually processed. Also added some debugging info and warning to catch problems with parsing. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/input_ova.ml | 8 +++++++- 1 file

The OVF standard allows the use of SHA256 hashes in the manifest file. Adding support for this. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/input_ova.ml | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/v2v/input_ova.ml b/v2v/input_ova.ml index 44e41ed..3c1a296 100644 --- a/v2v/input_ova.ml +++ b/v2v/input_ova.ml @@ -133,7 +133,7 @@

The regular expression for parsing the manifest line was wrong. There is a mandatory space between '=' and the hash. Another problem was that only the first line of the manifest file was actually processed. Also added some debugging info and warning to catch problems with parsing. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/input_ova.ml | 8 +++++++- 1 file

Hi I have installed the puppet master daemon and a puppet client but the puppet client is not periodically reloading the manifest, even though the client connects successfully and applies the manifest when started up the first time. My simple test manifest looks as follows: node default { file {"/home/ubuntuvm1/test.txt": mode => 777 } } Is it possible to set the

The regular expression for parsing the manifest line was wrong. There is a mandatory space between '=' and the hash. Another problem was that only the first line of the manifest file was actually processed. Also added some debugging info and warning to catch problems with parsing. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/input_ova.ml | 8 +++++++- 1 file

On Thu, 29 Sep 2016 15:53:18 +0200 Pino Toscano <ptoscano@redhat.com> wrote: > On Thursday, 29 September 2016 14:59:14 CEST Tomáš Golembiovský wrote: > > The regular expression for parsing the manifest line was wrong. There is > > a mandatory space between '=' and the hash. > > > > Another problem was that only the first line of the manifest file was >

This series fixes and enhances parsing of the OVA manifest file. The changes are: - Added mandatory space to the regexp - Process all lines in the file, not just one - Warn on improperly formated lines - Support SHA256 hashes Tomáš Golembiovský (2): v2v: ova: fix checking of the manifest file v2v: ova: support SHA256 hashes in manifest v2v/input_ova.ml | 27 ++++++++++++++++++--------- 1

On Fri, Sep 30, 2016 at 12:55:05PM +0200, Tomáš Golembiovský wrote: > > On Thu, 29 Sep 2016 15:53:18 +0200 > Pino Toscano <ptoscano@redhat.com> wrote: > > > On Thursday, 29 September 2016 14:59:14 CEST Tomáš Golembiovský wrote: > > > The regular expression for parsing the manifest line was wrong. There is > > > a mandatory space between '=' and

This series fixes and enhances parsing of the OVA manifest file. The changes are: - Added mandatory space to the regexp - Process all lines in the file, not just one - Warn on improperly formated lines - Support SHA256 hashes v1 -> v2: rebased on to master to make use of the Checksums module v2 -> v3: - changed debug/warning messages in first patch according to Richard's suggestions

The OVF standard allows the use of SHA256 hashes in the manifest file. Adding support for this. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/input_ova.ml | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/v2v/input_ova.ml b/v2v/input_ova.ml index 513fe30..5420c85 100644 --- a/v2v/input_ova.ml +++ b/v2v/input_ova.ml @@ -133,7 +133,7