Is there a right/approved/standard way to create hiera resources for forge
modules that don't do it on their own? (This is a question about the right
way to structure my Puppet code. I'm not asking how to use
hiera_create_resources.)
To create resources from hiera definitions in the past, I've used wrapper
classes, the quickshiftn-hiera class (an abandoned fork of hunner-hiera
that creates hiera resources without defining them in manifests), and small
class I wrote to do the job. None of them work all that well.
Let me give you an example of the structuring problem I'm running into:
Say I want to install Elasticsearch. I go to the forge, I install the
module, I include the class in Hiera, and define an instance, like so:
---
classes:
- 'elasticsearch'
elasticsearch::ensure: 'present'
elasticsearch::manage_repo: true
elasticsearch::repo_version: '1.7'
elasticsearch::instance:
'elasticsearch': {}
Elasticsearch installs, but no instance is created because the
elasticsearch-elasticsearch module doesn't create any hiera resources. So,
what's the right way to create the instance?
Thanks!
--
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/8e5a0724-91ee-4688-8fec-744a1f678e19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
