Details
-
Type:
Improvement
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: PUP 6.24.0, PUP 7.9.0
-
Component/s: None
-
Labels:
-
Template:customfield_10700 226260
-
Acceptance Criteria:
-
Epic Link:
-
Team:Coremunity
-
Sprint:Platform Core KANBAN
-
Release Notes:Enhancement
-
Release Notes Summary:Previously, if a template contained a BOM, then it was preserved by the `template` function, and would end up in the resulting file or PowerShell command. Now we pass the `bom` option when reading the file, which strips the BOM as it is read.
-
QA Risk Assessment:Needs Assessment
Description
See additional details in MODULES-1996 / PUP-6447.
The basic gist is that internal calls to read, like the one made by template loading with Puppet::FileSystem.read_preserve_line_endings, do not specify the "allow bom" flag when reading UTF-8 files.
This should be a straightforward addition that allows templates (for instance PowerShell templates that were once PS1 files created by PowerShell ISE that have a leading BOM) to properly remove the leading BOM.
Attachments
Issue Links
- relates to
-
PUP-6447 Allow UTF8 files to have a leading BOM to be more tolerant of files produced on Windows
-
- Accepted
-
-
-
- Closed
-
