-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Updating with Patch changes #12149
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
Updating with Patch changes #12149
Conversation
|
Hi, @viv-liu 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] |
Swagger Validation Report
Only 10 items are listed, please refer to log for more details.
|
| Rule | Message |
|---|---|
| The operation 'Devices_SetComponentProperties' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. New: Microsoft.IoTCentral/preview/2019-10-28-preview/iotcentral.json#L1819 |
|
| The operation 'Devices_UpdateComponentProperties' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. New: Microsoft.IoTCentral/preview/2019-10-28-preview/iotcentral.json#L1853 |
|
| The operation 'Devices_SetModuleComponentProperties' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. New: Microsoft.IoTCentral/preview/2019-10-28-preview/iotcentral.json#L2169 |
|
| The operation 'Devices_UpdateModuleComponentProperties' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. New: Microsoft.IoTCentral/preview/2019-10-28-preview/iotcentral.json#L2206 |
|
| The operation 'Devices_SetModuleProperties' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. New: Microsoft.IoTCentral/preview/2019-10-28-preview/iotcentral.json#L2303 |
|
| The operation 'Devices_UpdateModuleProperties' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. New: Microsoft.IoTCentral/preview/2019-10-28-preview/iotcentral.json#L2338 |
|
| The operation 'Devices_SetProperties' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. New: Microsoft.IoTCentral/preview/2019-10-28-preview/iotcentral.json#L2427 |
|
| The operation 'Devices_UpdateProperties' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. New: Microsoft.IoTCentral/preview/2019-10-28-preview/iotcentral.json#L2459 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️[Staging] Cross Version BreakingChange (Base on preview version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️[Staging] Cross Version BreakingChange (Base on stable version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
|
Swagger pipeline restarted successfully, please wait for status update in this comment. |
|
Hi, @viv-liu 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] |
...cation/iotcentral/data-plane/Microsoft.IoTCentral/preview/2019-10-28-preview/iotcentral.json
Show resolved
Hide resolved
|
Hi @viv-liu, 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. |
|
NewApiVersionRequired reason: |
|
Hi, @viv-liu. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
...cation/iotcentral/data-plane/Microsoft.IoTCentral/preview/2019-10-28-preview/iotcentral.json
Show resolved
Hide resolved
jhendrixMSFT
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.
Can you pleas also address the Avocado failures https://github.com/Azure/azure-rest-api-specs/pull/12149/checks?check_run_id=1572822106
Also looks like the prettier check is failing however the build is gone (can trigger a new one).
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
Hi @viv-liu, Your PR has some issues. Please fix the CI sequentially by following the order of
|
| } | ||
| }, | ||
| "delete": { | ||
| "operationId": "ContinuousDataExports_Remove", |
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 and not 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.
For some generated languages, delete is keyword, for example in typescript, generated code change to "deletemethod()", but use remove we can keep it "remove().
|
This is good to go. @lirenhe @jhendrixMSFT can you merge this? |
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
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.