azure-rest-api-specs icon indicating copy to clipboard operation
azure-rest-api-specs copied to clipboard

Add a new property to support Granular access control in NSP.

Open manishrw opened this issue 1 year ago • 5 comments

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.

[!NOTE] As of January 2024 there is no PR assignee. This is expected. See https://aka.ms/azsdk/pr-arm-review.

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)

  • For help with Step 2 / "ARM review", see https://aka.ms/azsdk/pr-arm-review.
Click here to see the diagram footnotes

Diagram footnotes

[1] See ARM review queue (for PR merge queues, see [2]).
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
The ARM reviewer on-call engineer visits the merge queue twice a day, so the approximate ETA for merges is 12 - 24 hours.

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

  • [ ] New resource provider.
  • [ ] New API version for an existing resource provider. (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 OpenAPI spec 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 suppressions guide 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.
  • For help with PR workflow diagram Step 2 (ARM review), see https://aka.ms/azsdk/pr-arm-review.
  • 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.

manishrw avatar Jan 23 '24 10:01 manishrw

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ The required check named Swagger LintDiff has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it.

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]
There are no breaking changes.
️⚠️Breaking Change(Cross-Version): 3 Warnings warning [Detail]
compared swaggers (via Oad v0.10.4)] new version base version
network.json 2023-09-01-preview(a59ce74) 2023-09-01(main)
network.json 2023-09-01-preview(a59ce74) 2023-08-01-preview(main)
networkSecurityPerimeter.json 2023-09-01-preview(a59ce74) 2023-08-01-preview(main)

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

Rule Message
:warning: 1029 - ReadonlyPropertyChanged The read only property has changed from 'true' to 'false'.
New: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L1624:9
Old: Microsoft.Network/preview/2023-08-01-preview/networkSecurityPerimeter.json#L1540:9
:warning: 1029 - ReadonlyPropertyChanged The read only property has changed from 'true' to 'false'.
New: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L1579:9
Old: Microsoft.Network/preview/2023-08-01-preview/networkSecurityPerimeter.json#L1495:9
:warning: 1033 - RemovedProperty The new version is missing a property found in the old version. Was 'serviceTags' renamed or removed?
New: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L1539:7
Old: Microsoft.Network/preview/2023-08-01-preview/networkSecurityPerimeter.json#L1455:7
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️❌LintDiff: 39 Errors, 72 Warnings failed [Detail]
compared tags (via openapi-validator v2.1.6) new version base version
package-2023-09-preview package-2023-09-preview(a59ce74) default(main)

[must fix]The following errors/warnings are introduced by current PR:

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

Rule Message Related RPC [For API reviewers]
OperationsAPIImplementation Operations API must be implemented for 'Microsoft.Network'.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L1
MissingTypeObject The schema 'ProxyResource' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L171
ResourceNameRestriction The resource name parameter 'networkSecurityPerimeterName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L37
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'networkSecurityPerimeterName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L278
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'profileName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L278
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'networkSecurityPerimeterName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L392
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'networkSecurityPerimeterName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L443
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'profileName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L443
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'accessRuleName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L443
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'networkSecurityPerimeterName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L560
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'profileName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L560
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'networkSecurityPerimeterName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L614
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'associationName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L614
RPC-Uri-V1-05
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/preview/2023-09-01-preview/networkSecurityPerimeter.json#L701
RPC-Delete-V1-01
ResourceNameRestriction The resource name parameter 'networkSecurityPerimeterName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L738
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'networkSecurityPerimeterName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L789
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'associationName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L789
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'networkSecurityPerimeterName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L884
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'profileName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L884
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'accessRuleName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L884
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'networkSecurityPerimeterName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L943
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'linkName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L943
RPC-Uri-V1-05
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/preview/2023-09-01-preview/networkSecurityPerimeter.json#L1030
RPC-Delete-V1-01
ResourceNameRestriction The resource name parameter 'networkSecurityPerimeterName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L1070
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'networkSecurityPerimeterName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L1121
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'linkName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L1121
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'networkSecurityPerimeterName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L1163
RPC-Uri-V1-05
ResourceNameRestriction The resource name parameter 'linkReferenceName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L1163
RPC-Uri-V1-05
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/preview/2023-09-01-preview/networkSecurityPerimeter.json#L1207
RPC-Delete-V1-01
ResourceNameRestriction The resource name parameter 'networkSecurityPerimeterName' should be defined with a 'pattern' restriction.
Location: Microsoft.Network/preview/2023-09-01-preview/networkSecurityPerimeter.json#L1247
RPC-Uri-V1-05


The following errors/warnings exist before current PR submission:

Rule Message
MissingTypeObject The schema 'ErrorDetails' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L38
MissingTypeObject The schema 'Error' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L55
MissingTypeObject The schema 'CloudError' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L83
MissingTypeObject The schema 'CloudErrorBody' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L93
MissingTypeObject The schema 'AzureAsyncOperationResult' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L118
MissingTypeObject The schema 'Resource' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L140
MissingTypeObject The schema 'SubResource' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L197
MissingTypeObject The schema 'TagsObject' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L207
MissingTypeObject The schema 'ManagedServiceIdentity' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L272
AvoidAnonymousTypes Inline/anonymous models must not be used, instead define a schema with a model name in the 'definitions' section and refer to it. This allows operations to share the models.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L300
ProvisioningStateValidation ProvisioningState must have terminal states: Succeeded, Failed and Canceled.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L320
MissingTypeObject The schema 'ExtendedLocation' is considered an object but without a 'type:object', please add the missing 'type:object'.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L394
XmsParameterLocation The parameter 'SubscriptionIdParameter' is defined in global parameters section without 'x-ms-parameter-location' extension. This would add the parameter as the client property. Please ensure that this is exactly you want. If so, apply the extension 'x-ms-parameter-location': 'client'. Else, apply the extension 'x-ms-parameter-location': 'method'.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L409
XmsParameterLocation The parameter 'ApiVersionParameter' is defined in global parameters section without 'x-ms-parameter-location' extension. This would add the parameter as the client property. Please ensure that this is exactly you want. If so, apply the extension 'x-ms-parameter-location': 'client'. Else, apply the extension 'x-ms-parameter-location': 'method'.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L416
XmsParameterLocation The parameter 'ApiVersionVmssParameter' is defined in global parameters section without 'x-ms-parameter-location' extension. This would add the parameter as the client property. Please ensure that this is exactly you want. If so, apply the extension 'x-ms-parameter-location': 'client'. Else, apply the extension 'x-ms-parameter-location': 'method'.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L423
:warning: XmsIdentifierValidation Missing identifier id in array item property
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L69
:warning: XmsIdentifierValidation Missing identifier id in array item property
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L108
:warning: LocationMustHaveXmsMutability Property location must have 'x-ms-mutability':['read', 'create'] extension defined.
Location: Microsoft.Network/preview/2023-09-01-preview/network.json#L156
️️✔️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.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️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?

Swagger Generation Artifacts

️️✔️ApiDocPreview succeeded [Detail] [Expand]
 Please click here to preview with your @microsoft account. 
️️✔️SDK Breaking Change Tracking succeeded [Detail] [Expand]

Breaking Changes Tracking




️️✔️ azure-sdk-for-net succeeded [Detail] [Expand]
️️✔️ azure-sdk-for-net-track2 succeeded [Detail] [Expand]
  • ️✔️Succeeded [Logs] Generate from 04716508166d514bca4069a68c969332ea25a880. SDK Automation 14.0.0
    command	pwsh ./eng/scripts/Automation-Sdk-Init.ps1 ../azure-sdk-for-net_tmp/initInput.json ../azure-sdk-for-net_tmp/initOutput.json
    command	pwsh ./eng/scripts/Invoke-GenerateAndBuildV2.ps1 ../azure-sdk-for-net_tmp/generateInput.json ../azure-sdk-for-net_tmp/generateOutput.json
  • ️✔️Azure.ResourceManager.Network [View full logs]  [Preview SDK Changes]
    info	[Changelog]
️⚠️ azure-sdk-for-python-track2 warning [Detail]
  • ⚠️Warning [Logs] Generate from 04716508166d514bca4069a68c969332ea25a880. SDK Automation 14.0.0
    command	sh scripts/automation_init.sh ../azure-sdk-for-python_tmp/initInput.json ../azure-sdk-for-python_tmp/initOutput.json
    cmderr	[automation_init.sh] WARNING: azure-devtools 1.2.1 does not provide the extra 'ci-tools'
    cmderr	[automation_init.sh] WARNING: azure-devtools 1.2.1 does not provide the extra 'ci-tools'
    cmderr	[automation_init.sh] WARNING: Skipping azure-nspkg as it is not installed.
    command	sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json
    cmderr	[automation_generate.sh] notice
    cmderr	[automation_generate.sh]  New minor version of npm available! 10.2.3 -> 10.3.0
    cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.3.0>
    cmderr	[automation_generate.sh] npm notice Run `npm install -g [email protected]` to update!
    cmderr	[automation_generate.sh] npm notice
  • ️✔️track2_azure-mgmt-network [View full logs]  [Preview SDK Changes]
    info	[Changelog]
️⚠️ azure-sdk-for-java warning [Detail]
  • ⚠️Warning [Logs] Generate from 04716508166d514bca4069a68c969332ea25a880. SDK Automation 14.0.0
    command	./eng/mgmt/automation/init.sh ../azure-sdk-for-java_tmp/initInput.json ../azure-sdk-for-java_tmp/initOutput.json
    cmderr	[init.sh] [notice] A new release of pip is available: 23.0.1 -> 23.3.2
    cmderr	[init.sh] [notice] To update, run: pip install --upgrade pip
    cmderr	[init.sh] [notice] A new release of pip is available: 23.0.1 -> 23.3.2
    cmderr	[init.sh] [notice] To update, run: pip install --upgrade pip
    cmderr	[init.sh] Current
    cmderr	[init.sh]                                  Dload  Upload   Total   Spent    Left  Speed
    cmderr	[init.sh] 
      0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0  1036k      0 --:--:-- --:--:-- --:--:-- 1036k
    cmderr	[init.sh] Downloading https://nodejs.org/dist/v18.15.0/node-v18.15.0-linux-x64.tar.xz...
    cmderr	[init.sh] ########### 100.0%
    cmderr	[init.sh] Computing checksum with sha256sum
    cmderr	[init.sh] Checksums matched!
    command	./eng/mgmt/automation/generate.py ../azure-sdk-for-java_tmp/generateInput.json ../azure-sdk-for-java_tmp/generateOutput.json
  • ️✔️azure-resourcemanager-network-generated [View full logs]  [Preview SDK Changes]
️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]
  • ️✔️Succeeded [Logs] Generate from 04716508166d514bca4069a68c969332ea25a880. SDK Automation 14.0.0
    command	sh ./eng/scripts/automation_init.sh ../../../../../azure-sdk-for-go_tmp/initInput.json ../../../../../azure-sdk-for-go_tmp/initOutput.json
    command	generator automation-v2 ../../../../../azure-sdk-for-go_tmp/generateInput.json ../../../../../azure-sdk-for-go_tmp/generateOutput.json
  • ️✔️sdk/resourcemanager/network/armnetwork [View full logs]  [Preview SDK Changes]
    info	[Changelog] ### Features Added
    info	[Changelog]
    info	[Changelog] - New value `VirtualNetworkPrivateEndpointNetworkPoliciesNetworkSecurityGroupEnabled`, `VirtualNetworkPrivateEndpointNetworkPoliciesRouteTableEnabled` added to enum type `VirtualNetworkPrivateEndpointNetworkPolicies`
    info	[Changelog] - New field `Zones` in struct `BastionHost`
    info	[Changelog]
    info	[Changelog] Total 0 breaking change(s), 3 additive change(s).
️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]
  • ️✔️Succeeded [Logs] Generate from 04716508166d514bca4069a68c969332ea25a880. SDK Automation 14.0.0
    command	sh .scripts/automation_init.sh ../azure-sdk-for-js_tmp/initInput.json ../azure-sdk-for-js_tmp/initOutput.json
    warn	File azure-sdk-for-js_tmp/initOutput.json not found to read
    command	sh .scripts/automation_generate.sh ../azure-sdk-for-js_tmp/generateInput.json ../azure-sdk-for-js_tmp/generateOutput.json
  • ️✔️@azure/arm-network [View full logs]  [Preview SDK Changes]
    info	[Changelog] **Features**
    info	[Changelog]
    info	[Changelog]   - Interface BastionHost has a new optional parameter zones
    info	[Changelog]   - Enum KnownVirtualNetworkPrivateEndpointNetworkPolicies has a new value NetworkSecurityGroupEnabled
    info	[Changelog]   - Enum KnownVirtualNetworkPrivateEndpointNetworkPolicies has a new value RouteTableEnabled
️🔄 azure-resource-manager-schemas inProgress [Detail]
️⚠️ azure-powershell warning [Detail]
  • ⚠️Warning [Logs] Generate from 04716508166d514bca4069a68c969332ea25a880. SDK Automation 14.0.0
    command	sh ./tools/SwaggerCI/init.sh ../azure-powershell_tmp/initInput.json ../azure-powershell_tmp/initOutput.json
    command	pwsh ./tools/SwaggerCI/psci.ps1 ../azure-powershell_tmp/generateInput.json ../azure-powershell_tmp/generateOutput.json
  • ⚠️Az.network.DefaultTag [View full logs]  [Preview SDK Changes]
Posted by Swagger Pipeline | How to fix these errors?

Generated ApiView

Language Package Name ApiView Link
Go sdk/resourcemanager/network/armnetwork https://apiview.dev/Assemblies/Review/08ab188fdab64564bc46944e13addcf9?revisionId=18e566d664684ccc8d578e0f27df17f7
Java azure-resourcemanager-network-generated https://apiview.dev/Assemblies/Review/d496e631581f47bcab5c961219fc2258?revisionId=4ea1c30065d141418df13cd88d9e79e0
JavaScript @azure/arm-network https://apiview.dev/Assemblies/Review/c13fd66ecbcc4c2a9995c8a1f4187240?revisionId=4180733dc5df49f992f594b36d3e7340
.Net Azure.ResourceManager.Network There is no API change compared with the previous version

Hi @manishrw! 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.

Hi, @manishrw. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove no-recent-activity label.

Hi, @manishrw. The PR will be closed since the PR has no update for 28 days. If you still need the PR review to proceed, please reopen it and @ mention PR assignee.