On Thursday, May 25, 2017 at 6:51:32 PM UTC+2, Henrik Lindberg wrote:
>
>
> If the purpose was to provide defaults, simply place a hiera.yaml in 
> your module and keep the (default) data for the module there. 
>
> Hope that helps. 
>
>

Just to give some feedback.  I completed the migration.  I went for the 
route of moving the module specifc data into the hiera data dir in each 
module.
Some refactoring was needed.

An other issue that I ran into was that some module hiera data is encrypted 
with eyaml.  You can still use eyaml in module hieradata.  When running 
rspec tests you need to provide some fake private and public keys on the 
box doing the rspec tests.  (Assuming the rspec tests doesnt test for 
encryped values).  But the rspec still needs to be able to open those files 
and see them as valid private and public keys (but this can be different 
than on production).

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/495413f5-1da3-4979-8ef8-a3f17e96174b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to