-
Notifications
You must be signed in to change notification settings - Fork 3.3k
{Security} Mitigate security risk of subprocess
#30146
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
️✔️AzureCLI-FullTest
|
|
Hi @AllyW, |
️✔️AzureCLI-BreakingChangeTest
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
37b64ed to
424d1d7
Compare
|
|
az group showsubprocess for az group show
subprocess for az group showsubprocess
424d1d7 to
cf4f27c
Compare
xSageDan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested endpoints with azdev on a test subscription, got a correct result from API. Can confirm this is working. Thank you @AllyW
Related command
az security automation create_or_update
az security automation validate
Description
As denoted in doc: Azure CLI Subprocess Guidelines, if target cmd is an operation from SDK, developers should apply corresponding method from SDK directly, to mitigate security issues in
subprocessTesting Guide
History Notes
{Security}
az security automation create_or_update/validate: Replacesubprocesswith client sdk operation for resources group fetchThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.