best practice for publishing modules that use Hiera?
63 views
Skip to first unread message
treydock
unread,
May 9, 2012, 12:46:12 PM5/9/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to puppet...@googlegroups.com
I've begun moving some of my modules the using hiera lookups in place of parameters being defined in a host's node entry. For data such as that I figure I can document the format of what the module expects from the yaml files, but if I use hiera to replace the typical "module::params", how do I include that in a published module? All the docs I've seen seem to show using paths for hieradata that are not specific to a module. What's the best way to publish a module that has things like package names defined through hiera? How would someone installing such a module make the hiera yaml files distributed with the module available to hiera lookups ?