-
Notifications
You must be signed in to change notification settings - Fork 134
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
MSFT_xPackageResource: Fix PSSA Issues #131
Comments
The error here is fixed in #123 |
This is part of #160 |
I'll work on this one if you like, because I need to get a fix through for #52. |
I'm working through these and am finding that there is some contention over whether or not the PSUseShouldProcessForStateChangingFunction warning should actually be used: My feeling is that this warning:
Therefore I would propose that this warning is simply suppressed when it occurs in any Unit or Integration tests in any of these modules. |
@PlagueHO Yes agreed on that rule. Just posted the PSSA rule severity list for DSC Resource Kit. Haven't implemented this list in tests yet though. ^Note in this case it would be approved to suppress the PSSA rule 'PSAvoidGlobalVars' |
@kwirkykat - oh nice! Good idea on the PSSA List. As for the remaining rules, those are the only ones I've fixed. I noted the suppression of the PSAvoidGlobalVars one too. I'll submit my PR sometime today/tonight. Thanks for getting back to me so quick. I'll also get some other PRs through for the warnings on the other resources. |
The PowerShell Script Analyzer issues in MSFT_xPackageResource need to be fixed.


This is the current result of running Invoke-ScriptAnalyzer:
The text was updated successfully, but these errors were encountered: