[PUP-10105] regression: puppet resource --to_yaml should not emit puppet class tags - Puppet Jira Server

XML

Word

Printable

Release Notes:
Bug Fix
Release Notes Summary:
Fix puppet resource --to_yaml emitting puppet class tags (e.g Puppet::Util::Execution::ProcessOutput) by ensuring that PScalarDataType only checks the instance of String, and not other subclasses

This change caused a regression. The option --to_yaml no longer generates syntactically valid YAML.

Before pull request #7718:

mysql_database:

  PERCONA_SCHEMA:

    ensure : 'present'

    charset: 'utf8'

    collate: 'utf8_general_ci'

After pull request #7718:

mysql_database:

  PERCONA_SCHEMA:

    ensure: present

    charset: !ruby/string:Puppet::Util::Execution::ProcessOutput utf8

    collate: !ruby/string:Puppet::Util::Execution::ProcessOutput utf8_general_ci

relates to

PUP-9154 Can't load catalog that was previously saved as yaml

PUP-7808 puppet resource <...> --to_yaml mishandles structured resource values

PUP-10820 Binary, Sensitive, etc deferred results can corrupt the transaction store

PUP-11229 Update puppet `instance?` methods to use `instance_of?` instead of `is_a?`

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(4 mentioned in)