-
Notifications
You must be signed in to change notification settings - Fork 1.7k
ConvertTo-SecureString -AsPlainText doesn't always require -Force #8796
Copy link
Copy link
Closed
Labels
area-securityArea - Security module and conceptsArea - Security module and conceptsissue-doc-bugIssue - error in documentationIssue - error in documentation
Description
Prerequisites
- Write a descriptive title.
- Search the existing issues.
Summary of the new feature or changed behavior
To use the AsPlainText parameter, the Force parameter must also be included in the command.
That's not correct, on my local desktop. Example below.
However it is true when running my build on Azure Pipelines - my build just broke.
Please add some detail around when it is needed, and when it isn't? Thankyou.
PS C:\Code> $bar = ConvertTo-SecureString -AsPlainText 'foo'
PS C:\Code> $bar.GetType()
IsPublic IsSerial Name BaseType
-------- -------- ---- --------
True False SecureString System.Object
PS C:\Code> $PSVersionTable.PSVersion
Major Minor Patch PreReleaseLabel BuildLabel
----- ----- ----- --------------- ----------
7 1 2List of articles that need to be updated
Link to related PR in PowerShell/PowerShell repo
n/a
Link to related Issues in PowerShell/PowerShell repo
n/a
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area-securityArea - Security module and conceptsArea - Security module and conceptsissue-doc-bugIssue - error in documentationIssue - error in documentation