-
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
Adding changes for external soft delete #30296
base: main
Are you sure you want to change the base?
Adding changes for external soft delete #30296
Conversation
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
Generated ApiView
|
}, | ||
{ | ||
"name": "purge", | ||
"description": "Optional, used to purge soft deleted volume groups if set to 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.
Does this mean it will be permanent deleted?
What's the default value?
Please update the description to include these info and make it more clear.
Besides that, if this is for permanent delete:
- Permanent deleted blob parameter is hidden in storage SDK/PSH/CLI. Should we also hide this parameter in PSH/CLI/SDK?
- Why not use aligned parameter name/type as blob permanent delete?
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.
What is the blob permanent delete parameter name?
For blob, is it just allowed through portal then?
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.
What is the blob permanent delete parameter name?
See the the link in my first comment.
For blob, is it just allowed through portal then?
Blob permanent delete is allowed in rest API, but not SDK/CLI/PSH. I can't find it in Azure Portal, also not blob swagger.
Please confirm with feature PM, if this should be open in SDK/PSH/CLI. If not, as SDK/PSH/CLI are all generated from swagger, we should consider if add this to swagger. (rest API doc is also generated from swagger)
.../elasticsan/resource-manager/Microsoft.ElasticSan/preview/2024-07-01-preview/elasticsan.json
Show resolved
Hide resolved
.../elasticsan/resource-manager/Microsoft.ElasticSan/preview/2024-07-01-preview/elasticsan.json
Outdated
Show resolved
Hide resolved
.../elasticsan/resource-manager/Microsoft.ElasticSan/preview/2024-07-01-preview/elasticsan.json
Show resolved
Hide resolved
.../elasticsan/resource-manager/Microsoft.ElasticSan/preview/2024-07-01-preview/elasticsan.json
Outdated
Show resolved
Hide resolved
.../elasticsan/resource-manager/Microsoft.ElasticSan/preview/2024-07-01-preview/elasticsan.json
Outdated
Show resolved
Hide resolved
.../elasticsan/resource-manager/Microsoft.ElasticSan/preview/2024-07-01-preview/elasticsan.json
Show resolved
Hide resolved
It looks the SDK check only runs on latest stable API version, which has no change. @ArthurMa1978 Any idea how to make SDK validation on run on the new added preview API version in this PR? |
.../elasticsan/resource-manager/Microsoft.ElasticSan/preview/2024-07-01-preview/elasticsan.json
Outdated
Show resolved
Hide resolved
.../elasticsan/resource-manager/Microsoft.ElasticSan/preview/2024-07-01-preview/elasticsan.json
Outdated
Show resolved
Hide resolved
.../elasticsan/resource-manager/Microsoft.ElasticSan/preview/2024-07-01-preview/elasticsan.json
Outdated
Show resolved
Hide resolved
Added sign off as the latest commits after label where updated descriptions based on previous comments. |
ad2eb6c
to
675e9dd
Compare
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
...rosoft.ElasticSan/preview/2024-07-01-preview/examples/ElasticSans_Create_MaximumSet_Gen.json
Show resolved
Hide resolved
API change check APIView has identified API level changes in this PR and created following API reviews. |
9abf7b2
to
0a69b34
Compare
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
Pull request was closed
@@ -26,7 +26,7 @@ These are the global settings for the storagepool. | |||
|
|||
``` yaml | |||
openapi-type: arm | |||
tag: package-2024-05 | |||
tag: package-2024-07-01-preview |
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.
You should add a section for tag "package-2024-07-01-preview" in this file below.
], | ||
"nextLink": "axgbgugzotxistmtabpjczrkqbfy" | ||
} | ||
"body": {} |
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.
why remove the body?
} | ||
], | ||
"enforceDataIntegrityCheckForIscsi": true, | ||
"deleteRetentionPolicy": { |
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.
With this example, as the input parameter for VG create not include deleteRetentionPolicy, Do you mean the "deleteRetentionPolicy" will be enabled with 14 retentionPeriodDays even user not set it in create VG? If not, the result should keep the minium output from server to make sure swagger check will cover the real server behavior with least server output.
@@ -1018,6 +1061,69 @@ | |||
} | |||
} | |||
}, | |||
"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ElasticSan/elasticSans/{elasticSanName}/volumegroups/{volumeGroupName}/volumes/{volumeName}/restore": { |
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.
Why only volume can be restore, but volumn group can't be restore?
Adding new api version 2024-07-01-preview for external soft delete