On 10/28/16 1:45 PM, Christopher Wood wrote: > Here's a Friday sort of question. > > All the yaml emitters don't add the extra space that I can add as a person > editing a file to make things more readable. Or to be more accurate, I can't > manage it myself and I can't find one that does. > > Consider the readability of the two examples below when thinking about what > keys go with which classes. Also keep in mind that while example one may be > fine for many of us, lots more people will find it easier to work with yaml > using example two. > > So how would I auto-magically auto-paragraph hiera yaml to make it friendlier > for more people, while still keeping it syntactically valid? > > > Example one: > > --- > one::services::enabled: true > one::two::abc: 8.45 > one::two::three: this is the string > puppet4::ca_server: otherhostname > puppet4::server: hostname > > > 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 >
Hi Christopher, It sounds like you have two processes managing the same data - a program that emits YAML and people who also edit that YAML. If so, you would be better off by splitting that between two backends. Hiera can query the program that emits YAML directly as well as reading the YAML you modify manually. Best regards, -g -- Garrett Honeycutt @learnpuppet Puppet Training with LearnPuppet.com Mobile: +1.206.414.8658 -- 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/033cc1a3-3e17-993e-1a1e-bd4b87b815b1%40garretthoneycutt.com. For more options, visit https://groups.google.com/d/optout.
