-
Notifications
You must be signed in to change notification settings - Fork 5.4k
AzureCompute DiskRP 2025-01-02 release #35205
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
base: main
Are you sure you want to change the base?
Conversation
* Swagger changes for ConfidentialVMv2 * update description of importsecure and uploadpreparedsecure create options
* Adding supportedSecurityOption * Updating description for supportedSecurityOption * Fixing pretty check errors * Formatting file Disk_Create_FromAnAzureComputeGalleryImage.json * Fixing prettier issues --------- Co-authored-by: Varsha Sankar <[email protected]>
…eatures (#34917) * fixing typo elasticSanResourceId * Swagger changes for Instant Access Snapshot and Availability Policy features * missed file in previous commit * adding missed description AvailabilityPolicy * adding missed references * updating descriptions * fixing casing * refactoring * refactoring-2 * fixing model validation * changing camel case of defintion of SnapshotAccessState --------- Co-authored-by: Theodore Chang <[email protected]>
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
"modelAsString": true | ||
} | ||
}, | ||
"instantAccessDurationMinutes": { |
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.
@PrambMS, could you please add?
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.
added minimu. per @PrambMS , there is no set maximum for the property
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.
minimum added. per @PrambMS , there is no set maximum
"format": "int64", | ||
"description": "“For snapshots created from Premium SSD v2 or Ultra disk, this property determines the time in minutes the snapshot is retained for instant access to enable faster restore." | ||
}, | ||
"securityMetadataUri": { |
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.
added
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.
We always use type: string for all these attributes, pls refer similar attributes like sourceUri, securityDataUri .
"type": "string", | ||
"description": "A SAS uri for accessing a VM guest state." | ||
}, | ||
"securityMetadataAccessSAS": { |
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.
@aayushkher please see ARM's 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.
This attribute has been decided on the basis of existing attributes, pls refer accessSAS and securityDataAccessSAS.
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.
to stay consistent with it sibling properties, which end in "SAS", we won't rename the property. But I did add x-ms-secret and format uri
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.
This attribute is a user SAS which must be shown to customers to download/upload contents to the given SAS. If the tag "x-ms-secret" automatically redacts the information in the response then this should not added for this attribute.
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.
Removing x-ms-secret because it is needs to be shown in CRUD operations
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting help
section at the bottom of this PR description.PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
Additional information
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiView
comment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.
Getting help
Purpose of this PR
andDue diligence checklist
.write access
per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Merge
comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queued
state, please add a comment with contents/azp run
.This should result in a new comment denoting a
PR validation pipeline
has started and the checks should be updated after few minutes.