-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Add deleteAll parameter #2078
Add deleteAll parameter #2078
Conversation
@@ -882,11 +892,11 @@ | |||
}, | |||
"cert": { | |||
"type": "string", | |||
"description": "The SSL cert data in PEM format encoded as base64 string" |
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.
No functional changes here. The cert/key were never being passed as base64 string so I'm fixing the comment.
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
@simongdavies this PR adds an optional query parameter. Adding |
@simongdavies can you please take a look? |
@@ -486,6 +489,13 @@ | |||
"type": "string", | |||
"description": "The version of the Microsoft.MachineLearningCompute resource provider API to use.", | |||
"required": true | |||
}, |
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.
@shutchings I don't entirely follow the usecase/intent of this parameter. Can you please share some more details with an example?
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.
When creating an operationalization cluster the resource is placed in the user's resource group and the supporting resources (ACS, app insights, ACR, storage account) are placed in a separate resource group. Right now when the user asks to delete the operationalization cluster only ACS and the operationalization cluster are deleted; ACR, storage accounts, and other resources are not deleted. This is so they still have access to their docker images, logs, telemetry, etc. But some users don't want any resources left behind when doing the delete since they no longer need any of it. With deleteAll=true all resources associated with the operationalization cluster are deleted.
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.
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.
@ravbhatnagar @anuchandy can I get some feedback on this? I'd like to start working on the .NET SDK/PowerShell changes.
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
Looks good. |
No modification for AutorestCI/azure-sdk-for-ruby |
If deleteAll=true then all resources that were created by MLC will get deleted. Currently only the operationalization cluster and ACS cluster get deleted which leaves behind all the ACS VMs.
PR information
api-version
in the path should match theapi-version
in the spec).Quality of Swagger