Le 09/07/2015 à 07:05:16-0700, jcbollinger a écrit
>
>
>
> No, at least not with HIera's built-in YAML back-end. YAML has no facility
> such as you describe, so to get it you would need to engage a YAML parser that
> supported such a thing as an extension.
Ok thanks.
>
> The hierarchy is the main tool available for combining data from multiple
> sources. If you don't want to use it for your purpose then you always have
> the
> alternative of writing a custom Hiera back-end, or, for some purposes, an
> altogether separate data lookup function.
>
> With that said, I'm not really following the nature of your problem. How
> would
> the availability of an 'include' statement mitigate the data-size issue you
> are
> concerned about?
>
Well, they are two not very important point :
1/ If i put all data inside my
node.yaml
it's visualy hard to edit that file
2/ If I put (for example)
asset.yaml
in all node using the hiearchy I feel that's not very clean.
I agree...it's not very important thing.
Regards.
--
Albert SHIH
DIO bâtiment 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/20150710122201.GB21009%40pcjas.obspm.fr.
For more options, visit https://groups.google.com/d/optout.
