[Hub Generated] Review request for Microsoft.Devices to add version stable/2021-07-02 #16492
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, @vikramadityab72 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] |
|
[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks. |
Swagger Validation Report
|
Swagger Generation Artifacts
|
|
Hi @vikramadityab72, Your PR has some issues. Please fix the CI sequentially by following the order of
|
This was referenced Oct 21, 2021
ruowan
reviewed
Oct 25, 2021
| @@ -35,9 +35,18 @@ tag: package-2021-07 | |||
| These settings apply only when `--tag=package-2021-07` is specified on the command line. | |||
|
|
|||
| ```yaml $(tag) == 'package-2021-07' | |||
| input-file: | |||
There was a problem hiding this comment.
You are using the same tag. package-2021-07. Pls use package-2021-07-01 and package-2021-07-02 for two swagger files.
There was a problem hiding this comment.
Btw, Why the two swagger file version are so close
There was a problem hiding this comment.
Because, there is open 2021-07-15 version, which is open, but not planning to merge soon, but it is enabled for the few customers.
openapi-workflow-bot
bot
added
the
WaitForARMFeedback
|
Hi, @vikramadityab72 your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board([email protected]). |
This was referenced Oct 25, 2021
j5lim
added
ARMSignedOff
This was referenced Nov 8, 2021
This was referenced Nov 8, 2021
|
/azp run |
LeiWang3
pushed a commit
to LeiWang3/azure-rest-api-specs
that referenced
this pull request
Mar 31, 2022
…table/2021-07-02 (Azure#16492) * Adds base for updating Microsoft.Devices from version stable/2021-07-01 to version 2021-07-02 * Updates readme * Updates API version in new specs and examples * iothub creation time * Add Data Residency Flag * Fixing the version in the readme file
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Changelog
Add a changelog entry for 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
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.
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 any of the following scenarios apply to the PR, request approval from the Breaking Change 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.