Skip to content

New Rule Suggestion - PSAvoidNonWhitelistedCmdletAliases #580

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

Closed
kilasuit opened this issue Jul 13, 2016 · 2 comments
Closed

New Rule Suggestion - PSAvoidNonWhitelistedCmdletAliases #580

kilasuit opened this issue Jul 13, 2016 · 2 comments

Comments

@kilasuit
Copy link
Contributor

The Usecase for this rule would be to allow those more advanced in using PowerShell to configure what Aliases dont flag up when the rule runs.

Also this would open up the Settings/Configuration/Profile discussion to a real world example case so also helps with the Design considerations that we would need to make at this point to be flexible going forward

@kapilmb
Copy link

kapilmb commented Jul 18, 2016

@kilasuit This would be functionally duplicate to the AvoidAlias rule except that you could customize the aliases. I think, the way to go about this is to get AvoidAlias use the whitelist (by means of settings/configuration file). We should be closing in on the settings/configuration design soon so as to enable feature like this (#518).

@kapilmb
Copy link

kapilmb commented Sep 8, 2016

We recently pushed a feature to pass parameters to rules via the settings file #611. Currently the scope of the feature is limited to the extent that we can pass parameters only to the PSAvoidUsingCmdletAliases rule. Since this feature obviates the need for PSAvoidNonWhitelistedCmdletAliases rule, will close this issue.

@kapilmb kapilmb closed this as completed Sep 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants