[PUP-5106] Add catalog_uuid to catalog Created: 2015/08/28  Updated: 2016/03/17  Resolved: 2016/01/26

Status: Closed
Project: Puppet
Component/s: None
Affects Version/s: None
Fix Version/s: PUP 4.4.0

Type: New Feature Priority: Normal
Reporter: Josh Cooper Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
blocks PDB-2126 Add the `catalog_uuid` and 'code_id' ... Closed
blocks PUP-4891 Add code_id and related fields to report Closed
blocks PUP-5702 Add code_id and catalog_uuid to report Closed
Epic Link: (Burnside) Direct Puppet: Client Static Catalog
Story Points: 1
Sprint: Client 2016-01-27
Release Notes: Not Needed


The catalog should generate a catalog_uuid, similar to how we generate a transaction_uuid, and it should be serialized with the catalog. Update the API docs and schema.

If the compiler is given the same set of inputs, and generates the equivalent catalogs, the catalog_uuid's should still be different.

Comment by William Hopper [ 2016/01/15 ]

Notes for review: we should now be able to find the catalog_uuid in the following places on the agent:

1) In the agent's cached catalog in /opt/puppetlabs/puppet/cache/client_data/catalog
2) Over the wire when running puppet agent with --http_debug enabled.

These UUIDs should match.

In addition, we should ensure that on a subsequent run using --use_cached_catalog, the cached catalog maintains its original catalog UUID, and that the server does not send a new catalog (and thus UUID) over the wire.

Comment by Steve Barlow [ 2016/01/26 ]

Josh Cooper William Hopper This ticket needs a docs field.

Comment by Steve Barlow [ 2016/01/26 ]

Set release notes to not needed since we decided to capture the doc work in a pre-docs ticket instead of in the individual work tickets for this feature

Generated at Sun Jul 12 23:09:00 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.