On Tuesday, 19 June 2012 03:26:14 UTC+10, Steve Traylen wrote:
>
>
> On Monday, 18 June 2012 13:02:33 UTC+2, Peter wrote:
>>
>> Hi Puppet Users,
>>
>> Essentially I would like to define a hiera.yaml file (just the hierarchy
>> and puppet datasource location) within my module and use it to clearly
>> separate Operating System differences to the default state. For example:
>>
> The hiera.yaml file is the global configuration for all paths, however it
> could contain a path of
> /etc/puppet/modules/%{module_name}/config/operatingsystem
> /etc/puppet/modules/%{module_name}/config/defaults
>
Hi Steve,
Thanks for the reply.
Although this will work it is not something I believe we should be aiming
for. I am hoping to eventually make some of the modules I am working on
available on the Puppet Forge.
Sorry you may have miss-understood me, I was not talking about over-riding
the hiera.yaml puppet file, I was talking about a version that describes
how hiera should interact with the puppet module it is currently
interacting with.
Using the solution you propose for module users it would we require
additional work updating and maintaining hiera.yaml settings that could be
non-trivial (what if a module uses a sub-directory data instead of config,
or OSFamily instead of OS, or other filters). Additionally what if the
module developer expects a particular ordering of the files but the module
users has something specific for there environment.
If we could implement a way for module developers to signal to hiera
information on how to interact with values specific to modules it provides
the best of both worlds:
* Module Users can specify the order of hiera values and control the
values they set; and
* Module Develoers can specify the location of hiera values and what is
the order is all without the module user having to work it out themselves.
Obviously in the puppet data extension to hiera it has been hardcoded to
look for a data.pp file so it could be configured to re-use some of the
other hiera code to interrogate a module hiera.yaml file.
Thanks,
Peter
--
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/-/Lq8aE-cfsMgJ.
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.
