Puppet users - Sep 2014 - puppet 3.6.2: future parser + extlookup() + environment based selector

Hi!

We use puppet 3.6.2 with several environments. One of them is vagrant based
environment called 'localdev' which is intended for local use only. Also
we keep all the secret data like passwords and related stuff in csv files which
reside in separate repository. We use extlookup() function to get the data from
these csv files. And of course this repo with secret data is unavailable for
those ones who work with vagrant based environment 'localdev'.

For example some of our code looks like this:

smtp_password => $::environment ? {
      default     => extlookup('smtp_password'),
      'localdev' => 'password'
},

When puppet is working with 'localdev' environment it does NOT try to
execute extlookup() function at all. That's what we need.

With current parser everything worked without any problems. But today I tried to
run our manifests with future parser enabled in 'localdev' environment.
And got the following error:

==> node1: Error: No match found for 'smtp_password' in any data file
during extlookup() on node node1.site
==> node1: Error: No match found for 'smtp_password' in any data file
during extlookup() on node node1.site

I assume that future parser tries to execute extlookup() function even if the
current environment is 'localdev'.

So I'm wondering if it is a bug? Or may be it is a normal behaviour of
future parser ?
 
I hope I explained everything correctly :)

Thanks in advance!

--
Best regards,
Sergey Arlashin

-- 
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-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/7D151217-05A3-45B7-940B-5638EFFA1622%40gmail.com.
For more options, visit https://groups.google.com/d/optout.