Fix: Robust netsh output parsing for Add-SslCert for Windows Server 2… #1253
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.
…022+ compatibility
Description: The prior version used indexes when parsing netsh output and would fail with Windows Server 2022. The new version uses field-name-based parsing for netsh output in Add-SslCert to ensure compatibility with Windows Server 2022 and future versions.
The one thing I didn't see was if there was a version number somewhere that needed bumped.
Documentation changes required: (N)
Added unit tests: (N)
Attached related issue: (Y) #1039 #1008 #919 #1058 #862
Checklist: