-
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
[Hub Generated] Review request for Microsoft.Devices to add version preview/2020-09-01-preview #11809
[Hub Generated] Review request for Microsoft.Devices to add version preview/2020-09-01-preview #11809
Conversation
Swagger Validation Report
|
Swagger Generation Artifacts
|
Hi, @mrohera Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. [email protected] |
@xccc-msft this is a preview version in support of a feature that is still in development hence the "breaking change". |
...ovisioningservices/resource-manager/Microsoft.Devices/preview/2020-09-01-preview/iotdps.json
Outdated
Show resolved
Hide resolved
Hi @mrohera, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. |
@mrohera I'm unable to merge as CI failure after breaking change detection. Just added the related label. |
@xccc-msft I have created the case per the workflow instructions. Please have a look. Thanks. |
Any update on the approval? |
@mrohera I'm not reviewer for breaking change. We have to wait for the approval. Thanks. |
@@ -1,7 +1,7 @@ | |||
{ | |||
"swagger": "2.0", | |||
"info": { | |||
"version": "2020-09-01-preview", | |||
"version": "2020-09-01-preview.1", |
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.
Is it valid to change version like this?
cc: @akning-ms
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.
I was given f/b that this is the guideline in order to make changes to an API that is still in development. I am checking with the approver and sharing the failure seen below.
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.
I've removed this version change since I added more changes and wanted the validations to re-run. I do not have clarity on what direction to proceed since the tests fail if this requirement were to be enforced.
Closing PR in favor of another PR with a new directory structure. |
This is the follow up PR: #12036 |
Re-opening this PR since ARM does not support "preview.1" style APIs. |
…review/2020-09-01-preview (Azure#11809) * Support userassigned identities for the KEK * Address PR comments * Update rev for breaking changes * Add identity information to the DPS description * Revert back version * Lint warnings
…review/2020-09-01-preview (Azure#11809) * Support userassigned identities for the KEK * Address PR comments * Update rev for breaking changes * Add identity information to the DPS description * Revert back version * Lint warnings
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Changelog
Please ensure to add changelog with this PR by answering the following questions.
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.
Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
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.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.