Issue #6006 has been updated by Nick Fagerlund.
I may be missing something here. It looks like the yaml terminus expects to be deserializing perfectly-formed Puppet::Node objects, which aren't as trivial to construct by hand as, e.g., the YAML expected by the exec terminus would be. In fact, it... looks like it's basically there to cache stuff retrieved from one of the other termini. What's the workflow you envision for taking advantage of the yaml terminus? (That is, how does the yaml come to exist, how is it managed and edited over its lifespan, how does the admin express minor differences between largely similar nodes, etc.) ---------------------------------------- Bug #6006: YAML node terminus for external nodes isn't documented anywhere https://projects.puppetlabs.com/issues/6006 Author: Nigel Kersten Status: Accepted Priority: Normal Assignee: Category: Target version: Keywords: Branch: Affected URL: We have an awesomely simple and powerful node_terminus for YAML node definitions, but we haven't documented it really. http://docs.puppetlabs.com/references/latest/indirection.html We should be documenting it here: http://docs.puppetlabs.com/guides/external_nodes.html with some examples. More people would use this than the exec terminus if they knew about it. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
