Both of those produce exactly the same content when loaded with the
default Ruby YAML parser, which should be how we load that stuff, and
everything works from my local testing too. :/
Can you dig deeper into what is going on inside your script? Perhaps
something else is going wrong?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/VChRtFes9wEJ.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
--
Daniel Pittman
⎋ Puppet Labs Developer – http://puppetlabs.com
♲ Made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/VChRtFes9wEJ.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> IDEA: Allow for a special YAML document to be spit out by custom ENCs
> when error conditions in the ENC are hit. It would contain information that
> can be shown in the console/reports ?
Sounds good. I am happy to look at extending the exec ENC protocol to
support that. I would take a patch, but if you just want to file a
feature request we will look to this when we next touch that protocol.
(Which is probably not that far off, for unrelated reasons.)