On Fri, Oct 28, 2016 at 7:45 PM, Christopher Wood <
christopher_w...@pobox.com> wrote:
>
>
> So how would I auto-magically auto-paragraph hiera yaml to make it
> friendlier for more people, while still keeping it syntactically valid?
>
>
> Example two:
>
> ---
> one::services::enabled: true
>
> one::two::abc: 8.45
> one::two::three: this is the string
>
> puppet4::ca_server: otherhostname
> puppet4::server: hostname
>
Another options not yet presented is to split the files out into the
classes they represent.
This can be done with something like this in your hiera.yaml using the
special variable %{calling_module}
---
:yaml:
:hierarchy:
- foo/%{calling_module}
Then, instead of having a foo.yaml with everything, you have a foo/one.yaml
and a foo/puppet.yaml (based on your above example). I like this
configuration in Hiera, and in fact Jerakia does something very similar by
default - grouping everything in one file can get very messy very quickly.
Using calling_module in hiera has a few limitations if you're doing crazy
things like hiera() calls across different modules, but if you are using
straight forward data binding lookups it works well. It's not quite an
answer to your question but it might help you keep things tidier.
Regards
Craig
--
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/CACxdKhGra34cP4Du37nwXMBy_0OFvgWeV%3Dcwgh_9gCdEvh9ddw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
