Servicebus : Added APIs to 2018-01-01-preview API version #11743
Conversation
This file contains 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
v-Ajnava
added
the
WaitForARMFeedback
|
Hi, @v-Ajnava 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] |
|
Hi, @v-Ajnava your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board([email protected]). cc @${PRAssignee} |
Swagger Generation Artifacts
|
| Rule | Message |
|---|---|
|
"logUrl":"https://apidrop.visualstudio.com/Content%20CI/_build/results?buildId=180912&view=logs&j=fd490c07-0b22-5182-fac9-6d67fe1e939b", "detail":"Run.ps1 failed with exit code 1 " |
|
Similar changes approved for EventHub : #11027 |
j5lim
approved these changes
Dec 2, 2020
j5lim
added
ARMSignedOff
ArcturusZhang
approved these changes
Dec 3, 2020
|
@zhenglaizhang for take a look API doc preview failure |
|
@v-Ajnava regarding the docs preview CI failure its because you are using same operation id prefix Namespaces_ in The operation id prefix is used as group name in docs CI, Currently rest api docs build doesn't support use same group name cross different swagger files. Can you help merge these same prefix sharing operations into single swagger file? |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
This was referenced Dec 9, 2020
This was referenced Dec 9, 2020
|
NewApiVersionRequired reason: |
added 3 commits
December 9, 2020 10:20
added 2 commits
December 10, 2020 01:15
|
Hi @v-Ajnava, 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. |
added 2 commits
December 10, 2020 01:45
This was referenced Dec 15, 2020
Closed
Closed
giromm2ms
pushed a commit
to giromm2ms/azure-rest-api-specs
that referenced
this pull request
Dec 20, 2020
* Added APIs to 2018-01-01-preview API version * added missing examples * added missign examples * update - removed unref examples * update * prettier check * update ptettier check all * Avocado fix * fix for ApiDocPreview * prettier check fix * Revert "prettier check fix" This reverts commit fcde91b. * Revert "fix for ApiDocPreview" This reverts commit 9789255. * schema fix * prettier fix * reverting all new changes * fix * update azureresourceschema
josuhazure
pushed a commit
to josuhazure/azure-rest-api-specs
that referenced
this pull request
Jan 6, 2021
* Added APIs to 2018-01-01-preview API version * added missing examples * added missign examples * update - removed unref examples * update * prettier check * update ptettier check all * Avocado fix * fix for ApiDocPreview * prettier check fix * Revert "prettier check fix" This reverts commit fcde91b. * Revert "fix for ApiDocPreview" This reverts commit 9789255. * schema fix * prettier fix * reverting all new changes * fix * update azureresourceschema
25 tasks
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.
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.