HomePhorge

(#14137) resource_type serialization naming conventions
47e519c8d880Unpublished

Unpublished Commit ยท Learn More

Repository Importing: This repository is still importing.

Description

(#14137) resource_type serialization naming conventions

This commit attempts to bring the serialized representation
of resource_type objects into better alignment with naming
conventions that we've established in our documentation
and elsewhere. In particular:

  • "resource_supertype" => "kind"
  • "hostclass" => "class"
  • "definition" => "defined_type"
  • "arguments" => "parameters"

These changes only affect the serialization (#to_pson/#from_pson).
The internal representation still uses the old terminology.
Ideally we'd just change the internals to conform to the
naming conventions, but that is a larger changeset than we
can reasonably tackle right now.

Details

Provenance
Chris Price <chris@puppetlabs.com>Authored on
vanmeeuwenPushed on Jun 2 2015, 2:22 PM
Parents
rPUb678cc4cc6be: Add ability to filter resource_type output by type
Branches
Unknown
Tags
Unknown

Event Timeline

Chris Price <chris@puppetlabs.com> committed rPU47e519c8d880: (#14137) resource_type serialization naming conventions (authored by Chris Price <chris@puppetlabs.com>).Apr 26 2012, 1:55 AM