Details
-
Type:
Task
-
Status: Resolved
-
Priority:
Normal
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:
Puppet Agent 5
-
Template:customfield_10700 194241
-
Team:Platform Core
-
Story Points:3
-
Sprint:Platform Core 2017-09-05, Agent 2017-06-28, Platform Core 2017-08-22
-
Release Notes:Not Needed
-
QA Risk Assessment:Automate
Description
In Puppet 5 we will be switching from using PSON by default to JSON. This requires that various interactions are validated to work as we expect them to. Here are the rough notes put together but John Duarte and myself based on a meeting we had with Josh Cooper
Agent <- Server <- Database
|
node info
|
catalog
|
file meta data
|
|
Agent -> Server -> Database
|
facts facts
|
reports catalog
|
reports
|
|
------------------------------------
|
v5 v5 v5
|
A: json (covered in CI)
|
B: fallback to pson catalog only (with binary data) (needs beaker testing) (John) (PUP-7681)
|
C: --preferred serialization format=pson on Agent (needs beaker testing) (John) (PUP-7729)
|
F: cached cat -> Always send json with escaped characters (needs beaker testing) (John) (PUP-7730)
|
------------------------------------
|
v3/4 v5 v5
|
D: pson (covered in PE upgrade testing)
|
F: cached cat -> Always send pson with escaped characters (manual) (Stan)
|
------------------------------------
|
v5 v4 v4
|
E: pson (expected downgrade to pson) (Stan)
|
F: cached cat -> Always send json with escaped characters (expected graceful failure) (manual) (Stan)
|
Attachments
Issue Links
- relates to
-
PUP-3852 Switch from PSON to JSON as default serialization format
-
- Closed
-
1.
|
acceptance: add preferred serialization format test |
|
Closed | Unassigned |
2.
|
acceptance: add test ensuring v5 sends report as json when catalog cached |
|
Closed | Unassigned |
