Add New ListNetworkGroupMembership API to network 2022 06 01 preview#21970
Merged
raych1 merged 14 commits intoAzure:dev-release-network-2022-06-01-previewfrom Jan 10, 2023
Conversation
|
Swagger pipeline can not start as the pull request has merge conflicts. |
|
Hi, @yanfa317 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. vscswagger@microsoft.com |
|
Swagger pipeline can not start as the pull request has merge conflicts. |
|
Swagger pipeline started successfully. If there is ApiView generated, it will be updated in this comment. |
ghost
added
the
…e-network-2022-06-01-preview
Swagger Validation Report
|
| compared tags (via openapi-validator v2.0.0) | new version | base version |
|---|---|---|
| package-2022-06-preview | package-2022-06-preview(5aebe1b) | default(dev-release-network-2022-06-01-preview) |
[must fix]The following errors/warnings are introduced by current PR:
| Rule | Message | Related RPC [For API reviewers] |
|---|---|---|
| Based on the response model schema, operation 'ListNetworkGroupMemberships' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.Network/preview/2022-06-01-preview/networkManagerGroupMembership.json#L58 |
️❌Avocado: 16 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
|
The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.Network/expressRouteCircuits/{}/arpTable is not in the default tag. Please make sure the missing API swaggers are in the default tag.readme: specification/network/resource-manager/readme.md json: Microsoft.Network/stable/2015-06-15/expressRouteCircuit.json |
|
The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.Network/expressRouteCircuits/{}/routesTable is not in the default tag. Please make sure the missing API swaggers are in the default tag.readme: specification/network/resource-manager/readme.md json: Microsoft.Network/stable/2015-06-15/expressRouteCircuit.json |
|
The default tag should contain all APIs. The API path /subscriptions/{}/providers/Microsoft.Network/virtualnetworks is not in the default tag. Please make sure the missing API swaggers are in the default tag.readme: specification/network/resource-manager/readme.md json: Microsoft.Network/stable/2015-06-15/virtualNetwork.json |
|
The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.Network/virtualnetworks is not in the default tag. Please make sure the missing API swaggers are in the default tag.readme: specification/network/resource-manager/readme.md json: Microsoft.Network/stable/2015-06-15/virtualNetwork.json |
|
The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.Network/virtualnetworks/{}/subnets/{} is not in the default tag. Please make sure the missing API swaggers are in the default tag.readme: specification/network/resource-manager/readme.md json: Microsoft.Network/stable/2015-06-15/virtualNetwork.json |
|
The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.Network/virtualnetworks/{}/subnets is not in the default tag. Please make sure the missing API swaggers are in the default tag.readme: specification/network/resource-manager/readme.md json: Microsoft.Network/stable/2015-06-15/virtualNetwork.json |
|
The default tag does not contains the latest API version. Please make sure the latest api version swaggers are in the default tag. readme: specification/network/resource-manager/readme.md json: Microsoft.Network/stable/2021-08-01/vmssNetworkInterface.json |
|
The default tag does not contains the latest API version. Please make sure the latest api version swaggers are in the default tag. readme: specification/network/resource-manager/readme.md json: Microsoft.Network/stable/2021-08-01/vmssPublicIpAddress.json |
|
The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.Network/interfaceEndpoints/{} is not in the default tag. Please make sure the missing API swaggers are in the default tag.readme: specification/network/resource-manager/readme.md json: Microsoft.Network/stable/2019-02-01/interfaceEndpoint.json |
|
The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.Network/interfaceEndpoints is not in the default tag. Please make sure the missing API swaggers are in the default tag.readme: specification/network/resource-manager/readme.md json: Microsoft.Network/stable/2019-02-01/interfaceEndpoint.json |
|
The default tag should contain all APIs. The API path /subscriptions/{}/providers/Microsoft.Network/interfaceEndpoints is not in the default tag. Please make sure the missing API swaggers are in the default tag.readme: specification/network/resource-manager/readme.md json: Microsoft.Network/stable/2019-02-01/interfaceEndpoint.json |
|
The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.Network/virtualWans/{}/p2sVpnServerConfigurations/{} is not in the default tag. Please make sure the missing API swaggers are in the default tag.readme: specification/network/resource-manager/readme.md json: Microsoft.Network/stable/2019-07-01/virtualWan.json |
|
The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.Network/virtualWans/{}/p2sVpnServerConfigurations is not in the default tag. Please make sure the missing API swaggers are in the default tag.readme: specification/network/resource-manager/readme.md json: Microsoft.Network/stable/2019-07-01/virtualWan.json |
|
The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.Network/firewallPolicies/{}/ruleGroups/{} is not in the default tag. Please make sure the missing API swaggers are in the default tag.readme: specification/network/resource-manager/readme.md json: Microsoft.Network/stable/2020-04-01/firewallPolicy.json |
|
The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.Network/firewallPolicies/{}/ruleGroups is not in the default tag. Please make sure the missing API swaggers are in the default tag.readme: specification/network/resource-manager/readme.md json: Microsoft.Network/stable/2020-04-01/firewallPolicy.json |
|
The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.Network/virtualNetworks/{}/bastionHosts is not in the default tag. Please make sure the missing API swaggers are in the default tag.readme: specification/network/resource-manager/readme.md json: Microsoft.Network/stable/2020-05-01/virtualNetwork.json |
️❌~[Staging] SwaggerAPIView: 0 Errors, 0 Warnings failed [Detail]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
Swagger Generation Artifacts
|
Generated ApiView
|
This was referenced Dec 22, 2022
|
Hi, @yanfa317 your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
openapi-workflow-bot
bot
added
ARMReview
WaitForARMFeedback
|
Hi @yanfa317, Your PR has some issues. Please fix the CI sequentially by following the order of
|
mentat9
reviewed
Jan 4, 2023
...urce-manager/Microsoft.Network/preview/2022-06-01-preview/networkManagerGroupMembership.json
Outdated
Show resolved
Hide resolved
openapi-workflow-bot
bot
removed
the
WaitForARMFeedback
openapi-workflow-bot
bot
added
the
WaitForARMFeedback
mentat9
added
the
ARMSignedOff
openapi-workflow-bot
bot
removed
the
WaitForARMFeedback
jago2136
reviewed
Jan 5, 2023
...urce-manager/Microsoft.Network/preview/2022-06-01-preview/networkManagerGroupMembership.json
Outdated
Show resolved
Hide resolved
jago2136
reviewed
Jan 5, 2023
...urce-manager/Microsoft.Network/preview/2022-06-01-preview/networkManagerGroupMembership.json
Show resolved
Hide resolved
jago2136
reviewed
Jan 5, 2023
...urce-manager/Microsoft.Network/preview/2022-06-01-preview/networkManagerGroupMembership.json
Show resolved
Hide resolved
jago2136
reviewed
Jan 5, 2023
...urce-manager/Microsoft.Network/preview/2022-06-01-preview/networkManagerGroupMembership.json
Show resolved
Hide resolved
jago2136
reviewed
Jan 5, 2023
...urce-manager/Microsoft.Network/preview/2022-06-01-preview/networkManagerGroupMembership.json
Outdated
Show resolved
Hide resolved
jago2136
reviewed
Jan 5, 2023
...urce-manager/Microsoft.Network/preview/2022-06-01-preview/networkManagerGroupMembership.json
Outdated
Show resolved
Hide resolved
jago2136
reviewed
Jan 5, 2023
...nager/Microsoft.Network/preview/2022-06-01-preview/examples/NetworkGroupMembershipsList.json
Outdated
Show resolved
Hide resolved
Contributor
|
Approved from my side (AVNM team member). |
qiaozha
reviewed
Jan 10, 2023
This was referenced Jan 10, 2023
raych1
approved these changes
Jan 10, 2023
11 tasks
raych1
pushed a commit
that referenced
this pull request
Mar 24, 2023
…23228) * Adds base for updating Microsoft.Network from version preview/2022-04-01-preview to version 2022-06-01-preview * Updates readme * Updates API version in new specs and examples * Add New ListNetworkGroupMembership API to network 2022 06 01 preview (#21970) * New networkManagerGroupMembership API * fix typo * New List NetworkGroupMembership API * fix * fix format * fix error * fix * fix as comments * fix
JoshLove-msft
pushed a commit
to JoshLove-msft/azure-rest-api-specs
that referenced
this pull request
Apr 25, 2023
…zure#23228) * Adds base for updating Microsoft.Network from version preview/2022-04-01-preview to version 2022-06-01-preview * Updates readme * Updates API version in new specs and examples * Add New ListNetworkGroupMembership API to network 2022 06 01 preview (Azure#21970) * New networkManagerGroupMembership API * fix typo * New List NetworkGroupMembership API * fix * fix format * fix error * fix * fix as comments * fix
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
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.
ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo. If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist (MS Employees Only):
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 the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
-[ ] 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. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.
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 you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.