[PUP-9110] Accept and produce ASCII_8BIT as Binary value Created: 2018/09/06 Updated: 2018/10/02 Resolved: 2018/09/26
|Fix Version/s:||PUP 6.0.1|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Epic Link:||6.y Rich Data|
|Release Notes:||Known Issue|
|Release Notes Summary:|| We did not quite finish the support for the Binary data type in time for 6.0.0. Before you start to use Binary in your manifests for anything except File content, you should be aware of the ticket
|QA Risk Assessment:||Needs Assessment|
The Binary data type (
The File type has been given support such that it accepts instances of Binary (i.e. Puppet::Pops::Types::PBinaryType::Binary to be precise. Other existing types and providers naturally does not know how to deal with that runtime value and can thus not immediately benefit from rich serialization of a Binary.
To resolve this, the Binary data type should be used in the catalog (rich data is on by default in puppet 6.0.0) but the runtime type on the agent should be changed from the special Binary to simply use ASCII_8BIT encoded String.
See the linked Predocs for a more in depth description.
|Comment by Henrik Lindberg [ 2018/09/14 ]|
We did not quite finish the support for the Binary data type in time for 6.0.0. Before you start to use Binary in your manifests for anything except File content, you should be aware of the ticket
|Comment by Josh Cooper [ 2018/09/26 ]|
Passed CI in e2f7ccfb7