-
Notifications
You must be signed in to change notification settings - Fork 5.6k
[Microsoft.ConfidentialLedger] Add new ARM API version preview/2024-09-19-preview #30653
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
[Microsoft.ConfidentialLedger] Add new ARM API version preview/2024-09-19-preview #30653
Conversation
Copied the files in a separate commit. This allows reviewers to easily diff subsequent changes against the previous spec.
Updated the API version from preview/2024-07-09-preview to preview/2024-09-19-preview.
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
Generated ApiView
|
|
The required check This new preview API version has been based off the latest preview version (2024-07-09-preview) and the previous PR / preview API version, which also had the same detected breaking changes, was eventually approved. Therefore, I've added the |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
…fidentialLedger-2024-09-19-preview
…fidentialLedger-2024-09-19-preview
|
API change check APIView has identified API level changes in this PR and created following API reviews. Microsoft.ConfidentialLedger |
|
/azp run |
|
Azure Pipelines successfully started running 4 pipeline(s). |
|
Waiting for team review before merging the PR |
…fidentialLedger-2024-09-19-preview
ryazhang-microsoft
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.
LGTM!
…9-19-preview (Azure#30653) * Copy files from preview/2024-07-09-preview Copied the files in a separate commit. This allows reviewers to easily diff subsequent changes against the previous spec. * Update version to preview/2024-09-19-preview Updated the API version from preview/2024-07-09-preview to preview/2024-09-19-preview. * Added tag for 2024-09-19-preview in readme file * Add enclave platform property * Fix prettier * Add application type property
…9-19-preview (Azure#30653) * Copy files from preview/2024-07-09-preview Copied the files in a separate commit. This allows reviewers to easily diff subsequent changes against the previous spec. * Update version to preview/2024-09-19-preview Updated the API version from preview/2024-07-09-preview to preview/2024-09-19-preview. * Added tag for 2024-09-19-preview in readme file * Add enclave platform property * Fix prettier * Add application type property
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection 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!
Purpose of this PR: add two new optional enum properties (
EnclavePlatformandApplicationType) to the ARM REST API specifications for Azure Confidential Ledger and Azure Managed CCF.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 ApiViewcomment 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 PRandDue diligence checklist.write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. 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.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.