YAML node terminus for external nodes isn't documented anywhere
|Assignee:||Nigel Kersten||% Done:|
We have an awesomely simple and powerful node_terminus for YAML node definitions, but we haven’t documented it really.
We should be documenting it here:
with some examples. More people would use this than the exec terminus if they knew about it.
#2 Updated by Nick Fagerlund about 2 years ago
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.)