-
Notifications
You must be signed in to change notification settings - Fork 395
Fix severity inconsistency in AvoidUsingConvertToSecureStringWithPlainText #470
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…PlainText rule. The severity showed by Get-ScriptAnalyzerRule and Invoke-ScriptAnalyzer for this rule were different. This was because scriptanalyzer defines two types of severities, viz., RuleSeverity and DiagnosticSeverity and the severity levels were not consistent. This commit makes the severity level consistent by setting them both to Warning.
a discussion (no related file): Comments from the review on Reviewable.io |
Reviewed 3 of 3 files at r1. Comments from the review on Reviewable.io |
Comments from the review on Reviewable.io |
Reviewed 9 of 9 files at r2. Comments from the review on Reviewable.io |
Review status: all files reviewed at latest revision, all discussions resolved. a discussion (no related file): Comments from the review on Reviewable.io |
Fix severity inconsistency in AvoidUsingConvertToSecureStringWithPlainText and UseIdenticalParametersDSC
This change is