[PUP-8528] Remove WriteOnlyYaml node terminus - Puppet Jira Server

XML

Word

Printable

Acceptance Criteria:

Hide

It should no longer be possible to set the node terminus to write_only_yaml. During a catalog compilation, puppetserver should never write the node's data to /opt/puppetlabs/server/data/...

Show
It should no longer be possible to set the node terminus to write_only_yaml. During a catalog compilation, puppetserver should never write the node's data to /opt/puppetlabs/server/data/...
Epic Link:
Puppet 6.0.0 Removals
Team:
Coremunity
Sprint:
Platform Core KANBAN

Release Notes:
Bug Fix
Release Notes Summary:

Hide
The write_only_yaml node terminus was used to "determine the list of
nodes that the master knows about" and predated widespread puppetdb
adoption. The write_only_yaml has been deprecated since 4.10.5, and
this commit removes it. Note this should result in a puppetserver speedup as it no longer will need to serialize node data as YAML to disk during a compile.

Show
The write_only_yaml node terminus was used to "determine the list of nodes that the master knows about" and predated widespread puppetdb adoption. The write_only_yaml has been deprecated since 4.10.5, and this commit removes it. Note this should result in a puppetserver speedup as it no longer will need to serialize node data as YAML to disk during a compile.

The WriteOnlyYaml node terminus was deprecated in 4.10.5 in commit f0890af6656de0fc16c85230f0596644e9ebcd29. It should be removed in 6.

relates to

MODULES-7667 Remove write_only_yaml behavior from catalog preview