(GH-8796) Clarify force parameter for ConvertTo-SecureString in 7+ #8797
Conversation
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
|
Docs Build status updates of commit 057894b: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
sdwheeler
reviewed
May 9, 2022
reference/7.0/Microsoft.PowerShell.Security/ConvertTo-SecureString.md
Outdated
Show resolved
Hide resolved
This commit clarifies the force parameter in PowerShell 7+, where it is no longer required but remains good practice to ensure backwards compatibility with older versions.
michaeltlombardi
force-pushed
the
gh-8796/main/clarify-force
branch
from
057894b to
9efe4a1
Compare
|
Docs Build status updates of commit 9efe4a1: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
sdwheeler
reviewed
May 10, 2022
reference/7.0/Microsoft.PowerShell.Security/ConvertTo-SecureString.md
Outdated
Show resolved
Hide resolved
sdwheeler
requested changes
May 10, 2022
reference/7.1/Microsoft.PowerShell.Security/ConvertTo-SecureString.md
Outdated
Show resolved
Hide resolved
reference/7.2/Microsoft.PowerShell.Security/ConvertTo-SecureString.md
Outdated
Show resolved
Hide resolved
reference/7.3/Microsoft.PowerShell.Security/ConvertTo-SecureString.md
Outdated
Show resolved
Hide resolved
sdwheeler
approved these changes
May 10, 2022
|
Docs Build status updates of commit f945a65: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
15 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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
This PR clarifies the force parameter in PowerShell 7+, where it is no longer required but remains good practice to ensure backwards compatibility with older versions.
-AsPlainTextdoesn't always require-Force#8796PR Context
Check the boxes below to indicate the content affected by this PR.
Repository or docset configuration
Conceptual documentation
Cmdlet reference & about_ topics
When changing cmdlet reference or about_ topics, the changes should be copied to all
relevant versions. Check the boxes below to indicate the versions affected by this change.
PR Checklist
please add the prefix
WIP:or[WIP]to the beginning of the title and remove the prefix whenthe PR is ready.