-
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
VirtualNetworkGateway identity fix #29376
Merged
GuptaVertika
merged 2 commits into
Azure:guptavertika/release-network-Microsoft.Network-official-2024-01-01
from
Khushboo-Baheti:vpnidentityFix
Jun 10, 2024
Merged
VirtualNetworkGateway identity fix #29376
GuptaVertika
merged 2 commits into
Azure:guptavertika/release-network-Microsoft.Network-official-2024-01-01
from
Khushboo-Baheti:vpnidentityFix
Jun 10, 2024
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
…tication. (Azure#29357) * Fix * Fix2 --------- Co-authored-by: Khushboo Baheti <khbaheti@microsoft.com>
Next Steps to Merge⌛ Please wait. Next steps to merge this PR are being evaluated by automation. ⌛ |
Swagger Validation Report
|
Compared specs (v0.10.9) | new version | base version |
---|---|---|
networkVirtualAppliance.json | 2024-01-01(fd4a7f2) | 2023-11-01(main) |
virtualNetworkGateway.json | 2024-01-01(fd4a7f2) | 2023-11-01(main) |
️⚠️
LintDiff: 0 Warnings warning [Detail]
Compared specs (v2.2.2) | new version | base version |
---|---|---|
package-2024-01 | package-2024-01(fd4a7f2) | package-2024-01(guptavertika/release-network-Microsoft.Network-official-2024-01-01) |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
Rule | Message |
---|---|
ResourceNameRestriction |
The resource name parameter 'virtualNetworkGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L37 |
DeleteResponseCodes |
Long-running delete operations must have responses with 202, 204 and default return codes. They also must have no other response codes. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L159 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L191 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L252 |
ResourceNameRestriction |
The resource name parameter 'virtualNetworkGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L325 |
ResourceNameRestriction |
The resource name parameter 'virtualNetworkGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L378 |
ParametersInPost |
gatewayVip is a query parameter. Post operation must not contain any query parameter other than api-version. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L385 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L415 |
ResourceNameRestriction |
The resource name parameter 'virtualNetworkGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L442 |
PostResponseCodes |
200 return code does not have a schema specified. LRO POST must have a 200 return code if only if the final response is intended to have a schema, if not the 200 return code must not be specified. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L443 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L475 |
ResourceNameRestriction |
The resource name parameter 'virtualNetworkGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L496 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L541 |
ResourceNameRestriction |
The resource name parameter 'virtualNetworkGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L562 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L607 |
ResourceNameRestriction |
The resource name parameter 'virtualNetworkGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L628 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L664 |
ResourceNameRestriction |
The resource name parameter 'virtualNetworkGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L685 |
ParametersInPost |
peer is a query parameter. Post operation must not contain any query parameter other than api-version. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L692 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L728 |
ResourceNameRestriction |
The resource name parameter 'virtualNetworkGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L749 |
ResourceNameRestriction |
The resource name parameter 'virtualNetworkGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L799 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L835 |
ResourceNameRestriction |
The resource name parameter 'virtualNetworkGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L856 |
ParametersInPost |
peer is a query parameter. Post operation must not contain any query parameter other than api-version. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L863 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L899 |
ResourceNameRestriction |
The resource name parameter 'virtualNetworkGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L920 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L959 |
ResourceNameRestriction |
The resource name parameter 'virtualNetworkGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L986 |
PostResponseCodes |
Long-running POST operations must have responses with 202 and default return codes. They must also have a 200 return code if only if the final response is intended to have a schema, if not the 200 return code must not be specified. They also must not have other response codes. Location: Microsoft.Network/stable/2024-01-01/virtualNetworkGateway.json#L987 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
SwaggerAPIView succeeded [Detail] [Expand]
️️✔️
TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️⌛
PR Summary pending [Detail]
️⌛
Automated merging requirements met pending [Detail]
Swagger Generation Artifacts
|
Rule | Message |
---|---|
RestBuild error |
"logUrl":"https://apidrop.visualstudio.com/Content%20CI/_build/results?buildId=433896&view=logs&j=fd490c07-0b22-5182-fac9-6d67fe1e939b", "detail":"Run.ps1 failed with exit code 128 " |
Generated ApiView
|
Khushboo-Baheti
changed the title
VietualNetworkGateway identity fix
VirtualNetworkGateway identity fix
Jun 10, 2024
GuptaVertika
approved these changes
Jun 10, 2024
GuptaVertika
merged commit Jun 10, 2024
fa39bf4
into
Azure:guptavertika/release-network-Microsoft.Network-official-2024-01-01
16 of 20 checks passed
rkmanda
pushed a commit
that referenced
this pull request
Jun 19, 2024
…29302) * Adds base for updating Microsoft.Network from version stable/2023-11-01 to version 2024-01-01 * Updates readme * Updates API version in new specs and examples * Add examples for Subnet peering and v6 Subnet peering. (#28827) Add examples for Subnet peering and v6 Subnet peering. --------- Co-authored-by: saurabh83 <saugu@microsoft.com> * Init (#29127) Co-authored-by: Abhishek Shah <shabhis@microsoft.com> * Adding the new response code to the 2024-01-01 version release of swagger to match the bugfix in 2023-11-01 (#29048) Co-authored-by: Arsheen Khatib (from Dev Box) <akhatib@microsoft.com> * Added NoHealthyBackendsBehavior (#28868) Added the property "NoHealthyBackendsBehavior" to the Probe properties. * VirtualNetworkGatewayConnection using key vault for authentication. (#28760) * Add parameters for cert based auth connection * retrigger checks * retrigger checks * lintDiff * Trigger Build * revert PATCH changes * fix * change managed identity to v5 * add format and description * rresolving conflict * resolving readme file * Revert "VirtualNetworkGatewayConnection using key vault for authentication. (#28760)" This reverts commit c37ec24. * Lint diff error suppress * Guptavertika/release network microsoft.network official 2024 01 01 (#29367) * added networkidentifier under vnet->subet->serviceendpoint * added format :armid and updated description * corrected the type * fixed response * response type fixed example --------- Co-authored-by: Bhupesh Bhatt <bhupeshbhatt@microsoft.com> * Adding GET operaton for Network Virtual Appliance Inbound Secuirty Rule (#29339) (#29375) * Fix for PR VirtualNetworkGatewayConnection using key vault for authentication. (#29357) (#29376) * Fix * Fix2 --------- Co-authored-by: Khushboo Baheti <khbaheti@microsoft.com> * Add CrossConnection Name as an optional query parameter in List ExpressRoute CrossConnection (#29251) * Add CrossConnection name as an optional query parameter for List CrossConnection * update example * Addressing comments * Change to OData filtering * Fix the parameter reference * Update --------- Co-authored-by: Jianqi Zhao <jianzhao@microsoft.com> * initial changes (#29235) * Changed type of networkIdentifier from PublicIPAddress to SubResource (#29469) * added networkidentifier under vnet->subet->serviceendpoint * added format :armid and updated description * corrected the type * fixed response * response type fixed example * Changed type of networkIdentifier from ./publicIpAddress.json#/definitions/PublicIPAddress to ./network.json#/definitions/SubResource --------- Co-authored-by: Bhupesh Bhatt <bhupeshbhatt@microsoft.com> --------- Co-authored-by: saurabh83 <splitt@gmail.com> Co-authored-by: saurabh83 <saugu@microsoft.com> Co-authored-by: Abhishek Shah <16267081+abhi7860@users.noreply.github.com> Co-authored-by: Abhishek Shah <shabhis@microsoft.com> Co-authored-by: AFK1194 <arsheen.khatib@gmail.com> Co-authored-by: Arsheen Khatib (from Dev Box) <akhatib@microsoft.com> Co-authored-by: Eugenio Peña García <70240915+EugenioPena@users.noreply.github.com> Co-authored-by: daweiwang-microsoft <165709729+daweiwang-microsoft@users.noreply.github.com> Co-authored-by: Bhupesh Kumar Bhatt <52891188+bhupeshbhatt1985@users.noreply.github.com> Co-authored-by: Bhupesh Bhatt <bhupeshbhatt@microsoft.com> Co-authored-by: Ashutosh Mishra <163998769+ashutmi@users.noreply.github.com> Co-authored-by: Khushboo Baheti <37917868+Khushboo-Baheti@users.noreply.github.com> Co-authored-by: Khushboo Baheti <khbaheti@microsoft.com> Co-authored-by: jianzhao1992 <125631957+jianzhao1992@users.noreply.github.com> Co-authored-by: Jianqi Zhao <jianzhao@microsoft.com> Co-authored-by: nimaller <71352534+nimaller@users.noreply.github.com>
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.
Choose a PR Template
Switch to "Preview" on this description then select one of the choices below.
Click here to open a PR for a Data Plane API.
Click here to open a PR for a Control Plane (ARM) API.