Sorry to burst you bubble....
The puppet backend has been 'broken' (intentionally?)

- https://projects.puppetlabs.com/issues/16321
-
https://mail.google.com/mail/u/1/?ui=2&shva=1#search/label%3Apuppet-users+pienaar/13a168982ad38854

Lots needs fixing...

Zipkid (Stefan)


On Fri, Oct 5, 2012 at 10:43 PM, Ellison Marks <gty...@gmail.com> wrote:

> Thanks for the reply. I'll probably start migrating things to the new
> "parameter" based lookup and a disk based hierarchy anyway, but it's good
> to know that my setup probably won't break immediately upon upgrading. ^_^
>
>
> On Friday, October 5, 2012 12:44:41 PM UTC-7, Nick Fagerlund wrote:
>>
>>
>>
>> On Friday, October 5, 2012 10:47:58 AM UTC-7, Ellison Marks wrote:
>>>
>>> I've been using Hiera and Hiera-Puppet with Puppet 2.7 for a while now,
>>> and I've been quite enjoying it. I just noticed the available update for
>>> Puppet and saw that Hiera was now part of core Puppet. However, I've been
>>> unable to parse exactly what parts made it over...
>>
>>
>> Yeah sorry, I'm working on clarifying that today.  The answer is: ALL OF
>> IT, but you might have to move your config file or change a setting.
>>
>> - Puppet has a hiera_config setting that defaults to $confdir/hiera.yaml.
>> It won't fall back to hiera's default conf file. If your conf is at
>> /etc/hiera.yaml, move it or tell puppet.conf where it is.
>> http://docs.puppetlabs.com/**references/latest/**
>> configuration.html#hieraconfig<http://docs.puppetlabs.com/references/latest/configuration.html#hieraconfig>
>> - The hierarchy itself works the same, including fact interpolation.
>> - All four hiera functions are still there. No need to change their names.
>> - The "puppet" backend is still there! That's one that we were planning
>> to remove at one point, and I don't yet have the whole story on how that
>> went down, but it did stay in. Or at least, it's in the source code; I
>> don't know how packages and gems deal with it, yet.
>> - The generic "lookup" function didn't happen. The built-in
>> "data_binding" code currently only applies to class parameters; we left an
>> expansion of it for a later date, once we have a deeper understanding of
>> users' needs and challenges.
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/pjyE89rYin4J.
>
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to