Skip to content

Jmegha123 network microsoft.network 2024 01 01 preview #27332

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

Draft
wants to merge 14 commits into
base: main
Choose a base branch
from

Conversation

jmegha123
Copy link
Member

@jmegha123 jmegha123 commented Jan 10, 2024

ARM (Control Plane) API Specification Update Pull Request

Tip: overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

diagram

Click here to see the details of Step 1

Breaking changes review (Diagram Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

  • The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
  • You believe there is no need for you to request breaking change approval, for any reason.
    Such claims must be reviewed, and the process is the same.
Click here to see the details of Step 2

ARM API changes review (Diagram Step 2)

  • If this PR is in purview of ARM review then automation will add the ARMReview label.
  • If you want to force ARM review, add the label yourself.
  • Proceed according to the diagram at the top of this comment.
Click here to see the diagram footnotes

Diagram footnotes

[1] ARM review queue (for merge queues, see [2])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])

If you need further help with anything, see Getting help section below.

Purpose of this PR

What's the purpose of this PR? Check all that apply. This is mandatory!

  • New API version. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
  • Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
  • Update existing version to fix swagger quality issues in S360.
  • Other, please clarify:
    • edit this with your clarification

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

  • I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
  • I have reviewed following Resource Provider guidelines, including
    ARM resource provider contract and
    REST guidelines (estimated time: 4 hours).
    I understand this is required before I can proceed to the Diagram Step 2, "ARM API changes Review", for this PR.

Additional information

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.

Getting help

  • First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
  • To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
  • For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
    and https://aka.ms/ci-fix.
  • If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
    This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
  • If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Copy link

openapi-pipeline-app bot commented Jan 10, 2024

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ Your PR has breaking changes in the generated SDK for go (label: CI-BreakingChange-Go). Refer to step 3 in the PR workflow diagram (even if your PR is for data plane, not ARM).
  • ❌ Your PR has breaking changes in the generated SDK for javascript (label: CI-BreakingChange-JavaScript). Refer to step 3 in the PR workflow diagram (even if your PR is for data plane, not ARM).
  • ❌ The required check named Swagger SpellCheck has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it.

Copy link

openapi-pipeline-app bot commented Jan 10, 2024

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]
There are no breaking changes.
️⚠️Breaking Change(Cross-Version): 72 Warnings warning [Detail]
compared swaggers (via Oad v0.10.4)] new version base version
applicationGateway.json 2024-01-01-preview(610b750) 2023-09-01(main)
applicationGatewayWafDynamicManifests.json 2024-01-01-preview(610b750) 2023-09-01(main)
applicationSecurityGroup.json 2024-01-01-preview(610b750) 2023-09-01(main)
availableDelegations.json 2024-01-01-preview(610b750) 2023-09-01(main)
availableServiceAliases.json 2024-01-01-preview(610b750) 2023-09-01(main)
azureFirewall.json 2024-01-01-preview(610b750) 2023-09-01(main)
azureFirewallFqdnTag.json 2024-01-01-preview(610b750) 2023-09-01(main)
azureWebCategory.json 2024-01-01-preview(610b750) 2023-09-01(main)
bastionHost.json 2024-01-01-preview(610b750) 2023-09-01(main)
checkDnsAvailability.json 2024-01-01-preview(610b750) 2023-09-01(main)
cloudServiceNetworkInterface.json 2024-01-01-preview(610b750) 2023-09-01(main)
cloudServicePublicIpAddress.json 2024-01-01-preview(610b750) 2023-09-01(main)
cloudServiceSwap.json 2024-01-01-preview(610b750) 2023-09-01(main)
customIpPrefix.json 2024-01-01-preview(610b750) 2023-09-01(main)
ddosCustomPolicy.json 2024-01-01-preview(610b750) 2023-09-01(main)
ddosProtectionPlan.json 2024-01-01-preview(610b750) 2023-09-01(main)
dscpConfiguration.json 2024-01-01-preview(610b750) 2023-09-01(main)
endpointService.json 2024-01-01-preview(610b750) 2023-09-01(main)
expressRouteCircuit.json 2024-01-01-preview(610b750) 2023-09-01(main)
expressRouteCrossConnection.json 2024-01-01-preview(610b750) 2023-09-01(main)
expressRoutePort.json 2024-01-01-preview(610b750) 2023-09-01(main)
expressRouteProviderPort.json 2024-01-01-preview(610b750) 2023-09-01(main)
firewallPolicy.json 2024-01-01-preview(610b750) 2023-09-01(main)
ipAllocation.json 2024-01-01-preview(610b750) 2023-09-01(main)
ipGroups.json 2024-01-01-preview(610b750) 2023-09-01(main)
loadBalancer.json 2024-01-01-preview(610b750) 2023-09-01(main)
natGateway.json 2024-01-01-preview(610b750) 2023-09-01(main)
network.json 2024-01-01-preview(610b750) 2023-09-01(main)
network.json 2024-01-01-preview(610b750) 2023-08-01-preview(main)
networkInterface.json 2024-01-01-preview(610b750) 2023-09-01(main)
networkManager.json 2024-01-01-preview(610b750) 2023-09-01(main)
networkManager.json 2024-01-01-preview(610b750) 2022-04-01-preview(main)
networkManagerActiveConfiguration.json 2024-01-01-preview(610b750) 2023-09-01(main)
networkManagerActiveConfiguration.json 2024-01-01-preview(610b750) 2022-04-01-preview(main)
networkManagerConnection.json 2024-01-01-preview(610b750) 2023-09-01(main)
networkManagerConnection.json 2024-01-01-preview(610b750) 2022-04-01-preview(main)
networkManagerConnectivityConfiguration.json 2024-01-01-preview(610b750) 2023-09-01(main)
networkManagerConnectivityConfiguration.json 2024-01-01-preview(610b750) 2022-04-01-preview(main)
networkManagerEffectiveConfiguration.json 2024-01-01-preview(610b750) 2023-09-01(main)
networkManagerEffectiveConfiguration.json 2024-01-01-preview(610b750) 2022-04-01-preview(main)
networkManagerGroup.json 2024-01-01-preview(610b750) 2023-09-01(main)
networkManagerGroup.json 2024-01-01-preview(610b750) 2022-04-01-preview(main)
networkManagerScopeConnection.json 2024-01-01-preview(610b750) 2023-09-01(main)
networkManagerScopeConnection.json 2024-01-01-preview(610b750) 2022-04-01-preview(main)
networkManagerSecurityAdminConfiguration.json 2024-01-01-preview(610b750) 2023-09-01(main)
networkManagerSecurityAdminConfiguration.json 2024-01-01-preview(610b750) 2022-04-01-preview(main)
networkProfile.json 2024-01-01-preview(610b750) 2023-09-01(main)
networkSecurityGroup.json 2024-01-01-preview(610b750) 2023-09-01(main)
networkVirtualAppliance.json 2024-01-01-preview(610b750) 2023-09-01(main)
networkWatcher.json 2024-01-01-preview(610b750) 2023-09-01(main)
operation.json 2024-01-01-preview(610b750) 2023-09-01(main)
privateEndpoint.json 2024-01-01-preview(610b750) 2023-09-01(main)
privateLinkService.json 2024-01-01-preview(610b750) 2023-09-01(main)
publicIpAddress.json 2024-01-01-preview(610b750) 2023-09-01(main)
publicIpPrefix.json 2024-01-01-preview(610b750) 2023-09-01(main)
routeFilter.json 2024-01-01-preview(610b750) 2023-09-01(main)
routeTable.json 2024-01-01-preview(610b750) 2023-09-01(main)
securityPartnerProvider.json 2024-01-01-preview(610b750) 2023-09-01(main)
serviceCommunity.json 2024-01-01-preview(610b750) 2023-09-01(main)
serviceEndpointPolicy.json 2024-01-01-preview(610b750) 2023-09-01(main)
serviceTags.json 2024-01-01-preview(610b750) 2023-09-01(main)
usage.json 2024-01-01-preview(610b750) 2023-09-01(main)
virtualNetwork.json 2024-01-01-preview(610b750) 2023-09-01(main)
virtualNetworkGateway.json 2024-01-01-preview(610b750) 2023-09-01(main)
virtualNetworkTap.json 2024-01-01-preview(610b750) 2023-09-01(main)
virtualRouter.json 2024-01-01-preview(610b750) 2023-09-01(main)
virtualWan.json 2024-01-01-preview(610b750) 2023-09-01(main)
vmssNetworkInterface.json 2024-01-01-preview(610b750) 2023-09-01(main)
vmssPublicIpAddress.json 2024-01-01-preview(610b750) 2023-09-01(main)
webapplicationfirewall.json 2024-01-01-preview(610b750) 2023-09-01(main)

The following breaking changes are detected by comparison with the latest preview version:

Only 12 items are listed, please refer to log for more details.

Rule Message
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/networkManagers/{networkManagerName}/listEffectiveVirtualNetworks' removed or restructured?
Old: Microsoft.Network/preview/2022-04-01-preview/networkManager.json#L418:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/networkManagers/{networkManagerName}/listActiveSecurityUserRules' removed or restructured?
Old: Microsoft.Network/preview/2022-04-01-preview/networkManagerActiveConfiguration.json#L143:5
⚠️ 1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/networkManagers/{networkManagerName}/networkGroups/{networkGroupName}/listEffectiveVirtualNetworks' removed or restructured?
Old: Microsoft.Network/preview/2022-04-01-preview/networkManagerGroup.json#L240:5
⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'EffectiveVirtualNetworksParameter' removed or renamed?
New: Microsoft.Network/preview/2024-01-01-preview/networkManager.json#L422:3
Old: Microsoft.Network/preview/2022-04-01-preview/networkManager.json#L476:3
⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'ActiveSecurityUserRule' removed or renamed?
New: Microsoft.Network/preview/2024-01-01-preview/networkManagerActiveConfiguration.json#L150:3
Old: Microsoft.Network/preview/2022-04-01-preview/networkManagerActiveConfiguration.json#L197:3
⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'ActiveDefaultSecurityUserRule' removed or renamed?
New: Microsoft.Network/preview/2024-01-01-preview/networkManagerActiveConfiguration.json#L150:3
Old: Microsoft.Network/preview/2022-04-01-preview/networkManagerActiveConfiguration.json#L197:3
⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'DefaultUserRulePropertiesFormat' removed or renamed?
New: Microsoft.Network/preview/2024-01-01-preview/networkManagerActiveConfiguration.json#L150:3
Old: Microsoft.Network/preview/2022-04-01-preview/networkManagerActiveConfiguration.json#L197:3
⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'UserRulePropertiesFormat' removed or renamed?
New: Microsoft.Network/preview/2024-01-01-preview/networkManagerActiveConfiguration.json#L150:3
Old: Microsoft.Network/preview/2022-04-01-preview/networkManagerActiveConfiguration.json#L197:3
⚠️ 1019 - RemovedEnumValue The new version is removing enum value(s) 'SecurityUser' from the old version.
New: Microsoft.Network/preview/2024-01-01-preview/networkManager.json#L504:11
Old: Microsoft.Network/preview/2022-04-01-preview/networkManager.json#L558:11
⚠️ 1019 - RemovedEnumValue The new version is removing enum value(s) 'SecurityUser' from the old version.
New: Microsoft.Network/preview/2024-01-01-preview/networkManager.json#L576:9
Old: Microsoft.Network/preview/2022-04-01-preview/networkManager.json#L625:9
⚠️ 1019 - RemovedEnumValue The new version is removing enum value(s) 'SecurityUser' from the old version.
New: Microsoft.Network/preview/2024-01-01-preview/networkManager.json#L613:11
Old: Microsoft.Network/preview/2022-04-01-preview/networkManager.json#L661:11
⚠️ 1019 - RemovedEnumValue The new version is removing enum value(s) 'SecurityUser' from the old version.
New: Microsoft.Network/preview/2024-01-01-preview/networkManager.json#L676:9
Old: Microsoft.Network/preview/2022-04-01-preview/networkManager.json#L724:9
️❌CredScan: 0 Errors, 0 Warnings failed [Detail]
️🔄LintDiff inProgress [Detail]
️❌Avocado: 48 Errors, 6 Warnings failed [Detail]

Only 12 items are listed, please refer to log for more details.

Rule Message
INCONSISTENT_API_VERSION The API version of the swagger is inconsistent with its file path.
readme: specification/network/resource-manager/readme.md
json: Microsoft.Network/preview/2024-01-01-preview/vmssNetworkInterface.json
INCONSISTENT_API_VERSION The API version of the swagger is inconsistent with its file path.
readme: specification/network/resource-manager/readme.md
json: Microsoft.Network/preview/2024-01-01-preview/vmssPublicIpAddress.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.Network/expressRouteCircuits/{}/ 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/preview/2015-05-01-preview/network.json
MISSING_APIS_IN_DEFAULT_TAG 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/preview/2015-05-01-preview/network.json
MISSING_APIS_IN_DEFAULT_TAG 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/preview/2015-05-01-preview/network.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.Network/expressRouteCircuits/{}stats 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/preview/2015-05-01-preview/network.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.Network/localNetworkGateways/{}/ 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/preview/2015-05-01-preview/network.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/microsoft.compute/virtualMachineScaleSets/{}/virtualMachines/{}/networkInterfaces 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/preview/2015-05-01-preview/network.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/microsoft.compute/virtualMachineScaleSets/{}/networkInterfaces 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/preview/2015-05-01-preview/network.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/microsoft.compute/virtualMachineScaleSets/{}/virtualMachines/{}/networkInterfaces/{} 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/preview/2015-05-01-preview/network.json
MISSING_APIS_IN_DEFAULT_TAG The default tag should contain all APIs. The API path /subscriptions/{}/resourceGroups/{}/providers/Microsoft.Network/publicIPAddresses/{}/ 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/preview/2015-05-01-preview/network.json
MISSING_APIS_IN_DEFAULT_TAG 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/preview/2015-05-01-preview/network.json
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️❌ModelValidation: 472 Errors, 0 Warnings failed [Detail]

Only 12 items are listed, please refer to log for more details.

Rule Message
INVALID_REQUEST_PARAMETER api-version 2021-05-01 is not equal to swagger version
Url: Microsoft.Network/preview/2024-01-01-preview/applicationGatewayWafDynamicManifests.json#L38:14
ExampleUrl: preview/2024-01-01-preview/examples/GetApplicationGatewayWafDynamicManifestsDefault.json#L2:17
INVALID_REQUEST_PARAMETER api-version 2021-05-01 is not equal to swagger version
Url: Microsoft.Network/preview/2024-01-01-preview/applicationGatewayWafDynamicManifests.json#L78:14
ExampleUrl: preview/2024-01-01-preview/examples/GetApplicationGatewayWafDynamicManifests.json#L2:17
LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
Url: Microsoft.Network/preview/2024-01-01-preview/applicationSecurityGroup.json#L66:22
ExampleUrl: preview/2024-01-01-preview/examples/ApplicationSecurityGroupDelete.json
LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
Url: Microsoft.Network/preview/2024-01-01-preview/azureFirewall.json#L66:22
ExampleUrl: preview/2024-01-01-preview/examples/AzureFirewallDelete.json
MISSING_RESOURCE_ID id is required to return in response of GET/PUT resource calls but not being provided
Url: Microsoft.Network/preview/2024-01-01-preview/azureFirewall.json#L788:47
ExampleUrl: preview/2024-01-01-preview/examples/AzureFirewallGet.json#L45:13
MISSING_RESOURCE_ID id is required to return in response of GET/PUT resource calls but not being provided
Url: Microsoft.Network/preview/2024-01-01-preview/azureFirewall.json#L908:39
ExampleUrl: preview/2024-01-01-preview/examples/AzureFirewallGet.json#L75:13
MISSING_RESOURCE_ID id is required to return in response of GET/PUT resource calls but not being provided
Url: Microsoft.Network/preview/2024-01-01-preview/azureFirewall.json#L1043:43
ExampleUrl: preview/2024-01-01-preview/examples/AzureFirewallGet.json#L124:13
MISSING_RESOURCE_ID id is required to return in response of GET/PUT resource calls but not being provided
Url: Microsoft.Network/preview/2024-01-01-preview/azureFirewall.json#L788:47
ExampleUrl: preview/2024-01-01-preview/examples/AzureFirewallGetWithZones.json#L49:13
MISSING_RESOURCE_ID id is required to return in response of GET/PUT resource calls but not being provided
Url: Microsoft.Network/preview/2024-01-01-preview/azureFirewall.json#L908:39
ExampleUrl: preview/2024-01-01-preview/examples/AzureFirewallGetWithZones.json#L79:13
MISSING_RESOURCE_ID id is required to return in response of GET/PUT resource calls but not being provided
Url: Microsoft.Network/preview/2024-01-01-preview/azureFirewall.json#L1043:43
ExampleUrl: preview/2024-01-01-preview/examples/AzureFirewallGetWithZones.json#L128:13
MISSING_RESOURCE_ID id is required to return in response of GET/PUT resource calls but not being provided
Url: Microsoft.Network/preview/2024-01-01-preview/azureFirewall.json#L788:47
ExampleUrl: preview/2024-01-01-preview/examples/AzureFirewallGetWithMgmtSubnet.json#L59:13
MISSING_RESOURCE_ID id is required to return in response of GET/PUT resource calls but not being provided
Url: Microsoft.Network/preview/2024-01-01-preview/azureFirewall.json#L908:39
ExampleUrl: preview/2024-01-01-preview/examples/AzureFirewallGetWithMgmtSubnet.json#L89:13
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️❌SpellCheck: 1 Errors, 0 Warnings failed [Detail]
Rule Message
HowToFix Unknown word (Conditon), please fix the error. See https://aka.ms/ci-fix#spell-check
path: Microsoft.Network/preview/2024-01-01-preview/webapplicationfirewall.json#L705:18
️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
️️✔️Automated merging requirements met succeeded [Detail] [Expand]
Posted by Swagger Pipeline | How to fix these errors?

Copy link

openapi-pipeline-app bot commented Jan 10, 2024

Swagger Generation Artifacts

️❌ApiDocPreview: 1 Errors, 0 Warnings failed [Detail]

Only -1 items are listed, please refer to log for more details.

Rule Message
️️✔️SDK Breaking Change Tracking succeeded [Detail] [Expand]

Only 0 items are rendered, please refer to log for more details.

️️✔️ azure-sdk-for-net succeeded [Detail] [Expand]

Only 0 items are rendered, please refer to log for more details.

️❌ azure-sdk-for-net-track2 failed [Detail]

Only 0 items are rendered, please refer to log for more details.

️⚠️ azure-sdk-for-python-track2 warning [Detail]

Only 0 items are rendered, please refer to log for more details.

️⚠️ azure-sdk-for-java warning [Detail]

Only 0 items are rendered, please refer to log for more details.

️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]

Only 0 items are rendered, please refer to log for more details.

️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]

Only 0 items are rendered, please refer to log for more details.

️🔄 azure-resource-manager-schemas inProgress [Detail]
️⚠️ azure-powershell warning [Detail]

Only 0 items are rendered, please refer to log for more details.

Posted by Swagger Pipeline | How to fix these errors?

Copy link

Hi @jmegha123! For review efficiency consideration, when creating a new API version, it is required to place API specs of the base version in the first commit, and push new version updates into successive commits. You can use OpenAPIHub to initialize the PR for adding a new version.
For more details refer to the wiki.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants