Dev deviceprovisioningservices microsoft.devices 2020 09 01 preview#10735
Conversation
[Staging] Swagger Validation Report
️✔️ |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
For the benefit of the reviewers, this preview version was created from the 2020-03-01 (stable) version and the "encryption" CMK properties were added over and above the existing stable API. |
azure-sdk-for-go - Release
|
azure-sdk-for-java - Release
|
Azure CLI Extension Generation - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-js - Release
|
azure-sdk-for-python - Release
|
azure-sdk-for-net - Release
|
Trenton Generation - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-python-track2 - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-resource-manager-schemas - Release
|
|
@xccc-msft, it appears that the failures in the gates seem unrelated to the changes and I am unsure how to proceed. Can you help with this? |
@NullMDR Can you please help? Thanks. |
|
The SDK generation failure could be ignored. |
|
Thanks for approving. How can I merge this PR? I am not authorized to merge. |
|
Can you add an example on how to use the CMK feature? |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Added sample PTAL. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Thank you for keeping the previous version as first commit for easier find the changes. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Thanks @chiragg4u for the sign off! What can I do to merge? All the required gate checkins are met. |
Hi @NullMDR , based on your comment above and since I have ARMSignedOff and all the required checks met, can this PR be merged. I cannot merge this since I am not authorized. |
…zure#10735) * Adds base for updating Microsoft.Devices from version stable/2020-03-01 to version 2020-09-01-preview * Updates readme * Updates API version in new specs and examples * Add CMK encryption properties * Add sample for CMK * Prettier format * Add example reference * Add encryption to response in example * Removing example for now since this is still WIP
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.
Please follow the link to find more details on PR review process.