docs: Add known issue for numeric string coercion in Windows PowerShell#1526
Open
Gijsreyn wants to merge 2 commits intoPowerShell:mainfrom
Open
docs: Add known issue for numeric string coercion in Windows PowerShell#1526Gijsreyn wants to merge 2 commits intoPowerShell:mainfrom
Gijsreyn wants to merge 2 commits intoPowerShell:mainfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new entry to the troubleshooting guide documenting a Windows PowerShell-specific failure mode where numeric-looking YAML strings (for string-typed schema properties) can be coerced to integers prior to schema validation.
Changes:
- Added a new known issue (t04) describing numeric string coercion to integers in Windows PowerShell.
- Documented expected error output, reproduction context, and suggested workarounds (use PowerShell 7+ and/or
--file -via stdin).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Summary
Whilst working on a fresh machine and adding docs for one of the built-in resources, working in Windows PowerShell revealed another known issue. This PR adds t04 to the troubleshooting guide documenting failures that can occur when running DSC configuration commands in Windows PowerShell containing string-typed properties quoted as "8080" (as an example).