The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:
Improve Puppet's handling of non-ASCII character encodings
|Assignee:||Charlie Sharpsteen||% Done:|
|Affected Puppet version:||Branch:|
This is an umbrella bug for issues related to Puppet’s handling of non-ASCII character encodings. Many of these issues crop up when running Puppet on Ruby 1.9.x and newer.
See the ‘related bugs’ field for a full list of issues.
#1 Updated by Anonymous almost 3 years ago
As a rough first pass at what it will take to provide proper data encoding support in puppet:
- Every manifest can declare its encoding
- Every command on the master that reads from the external world can declare and encode
- No encoding in manifests defaults to UTF-8
- No encoding in external reads defaults to binary
- Tagging of data in wire formats so we know how to interpret it on the other side
- Proper conversion to system locale of data when writing and source material is encoded (not binary)
- String manipulation in puppet has very strict no-conversion semantics
- Resource parameters are treated as binary unless the type declares otherwise
- If a binary parameter value is used for a non-binary parameter, an error is raised
Some of these are about basic support, others are about making a safe, usable system (strictness for instance).
- resolutions must encode their values in UTF-8 (no binary allowed?)