You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now it appears that the PSAvoidUsingPlainTextForPassword rule generates an error whenever it sees a variable called $Password that is not a SecureString. I have a Reset-DoPxDroplet function with a $Password parameter of type switch (System.Management.Automation.SwitchParameter) to allow me to reset the password on a droplet (VM). There is no use of secure string or string, just switch, so that I can make the appropriate REST API endpoint, yet this rule generates a warning anyway.
If I'm clearly defining the type of my $Password parameter as switch, which I am in this case, then this rule shouldn't even look at how I'm using that parameter. It should only complain if I have $Password that is not strongly typed, or that is of type string.
The text was updated successfully, but these errors were encountered:
Right now it appears that the PSAvoidUsingPlainTextForPassword rule generates an error whenever it sees a variable called $Password that is not a SecureString. I have a Reset-DoPxDroplet function with a $Password parameter of type switch (System.Management.Automation.SwitchParameter) to allow me to reset the password on a droplet (VM). There is no use of secure string or string, just switch, so that I can make the appropriate REST API endpoint, yet this rule generates a warning anyway.
If I'm clearly defining the type of my $Password parameter as switch, which I am in this case, then this rule shouldn't even look at how I'm using that parameter. It should only complain if I have $Password that is not strongly typed, or that is of type string.
The text was updated successfully, but these errors were encountered: