Fix runningOperationIds data type #22259

supriyajha-ms · 2023-01-20T09:39:02Z

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:

What's the purpose of the update?
- new service onboarding
- new API version
- update existing version for new feature
- update existing version to fix swagger quality issue in s360
- Other, please clarify
When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

I commit to follow the Breaking Change Policy of "no breaking changes"
I have reviewed the documentation for the workflow.
Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.

ARM API Review Checklist

Applicability: ⚠️

If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs

Adding new properties

All removals

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.
- Adding a new service
- Adding new API(s)
- Adding a new API version
  -[ ] 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.

openapi-workflow-bot · 2023-01-20T09:39:05Z

Hi, @supriyajha-ms Thanks for your PR. I am workflow bot for review process. Here are some small tips.

Please ensure to do self-check against checklists in first PR comment.

PR assignee is the person auto-assigned and responsible for your current PR reviewing and merging.

For specs comparison cross API versions, Use API Specs Comparison Report Generator

If there is CI failure(s), to fix CI error(s) is mandatory for PR merging; or you need to provide justification in PR comment for explanation. How to fix?

Any feedback about review process or workflow bot, pls contact swagger and tools team. [email protected]

openapi-pipeline-app · 2023-01-20T09:39:06Z

Swagger Validation Report

️❌BreakingChange: 4 Errors, 0 Warnings failed [Detail]

compared swaggers (via Oad v0.10.4)]	new version	base version
networkWatcher.json	2022-01-01(d55772b)	2022-01-01(main)
networkWatcher.json	2022-05-01(d55772b)	2022-05-01(main)

Rule	Message
`❌` 1023 - TypeFormatChanged	The new version has a different format than the previous one. New: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L2384:11 Old: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L2384:11
`❌` 1023 - TypeFormatChanged	The new version has a different format than the previous one. New: Microsoft.Network/stable/2022-05-01/networkWatcher.json#L2384:11 Old: Microsoft.Network/stable/2022-05-01/networkWatcher.json#L2384:11
`❌` 1026 - TypeChanged	The new version has a different type 'string' than the previous one 'integer'. New: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L2384:11 Old: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L2384:11
`❌` 1026 - TypeChanged	The new version has a different type 'string' than the previous one 'integer'. New: Microsoft.Network/stable/2022-05-01/networkWatcher.json#L2384:11 Old: Microsoft.Network/stable/2022-05-01/networkWatcher.json#L2384:11

️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]

There are no breaking changes.

️️✔️CredScan succeeded [Detail] [Expand]

There is no credential detected.

️⚠️LintDiff: 0 Warnings warning [Detail]

compared tags (via openapi-validator v2.0.0)	new version	base version
package-2022-01	package-2022-01(d55772b)	package-2022-01(main)
package-2022-05	package-2022-05(d55772b)	package-2022-05(main)

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 'networkWatcherName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L37
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L178
`❌` ResourceNameRestriction	The resource name parameter 'networkWatcherName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L344
`❌` ResourceNameRestriction	The resource name parameter 'networkWatcherName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L403
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L448
`❌` ResourceNameRestriction	The resource name parameter 'networkWatcherName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L472
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L517
`❌` ResourceNameRestriction	The resource name parameter 'networkWatcherName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L541
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L586
`❌` ResourceNameRestriction	The resource name parameter 'networkWatcherName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L610
`❌` ResourceNameRestriction	The resource name parameter 'packetCaptureName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L610
`❌` XmsResourceInPutResponse	The 200 response model for an ARM PUT operation must have x-ms-azure-resource extension set to true in its hierarchy.Operation: PacketCaptures_Create Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L611
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L773
`❌` ResourceNameRestriction	The resource name parameter 'networkWatcherName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L794
`❌` ResourceNameRestriction	The resource name parameter 'packetCaptureName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L794
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L834
`❌` ResourceNameRestriction	The resource name parameter 'networkWatcherName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L855
`❌` ResourceNameRestriction	The resource name parameter 'packetCaptureName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L855
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L898
`❌` ResourceNameRestriction	The resource name parameter 'networkWatcherName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L922
`❌` ResourceNameRestriction	The resource name parameter 'networkWatcherName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L975
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L1020
`❌` ResourceNameRestriction	The resource name parameter 'networkWatcherName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L1044
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L1089
`❌` ResourceNameRestriction	The resource name parameter 'networkWatcherName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L1113
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L1159
`❌` ResourceNameRestriction	The resource name parameter 'networkWatcherName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L1183
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L1229
`❌` ResourceNameRestriction	The resource name parameter 'networkWatcherName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L1253
`❌` LroLocationHeader	A 202 response should include an Location response header. Location: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L1298

️️✔️Avocado succeeded [Detail] [Expand]

Validation passes for Avocado.

️️✔️ApiReadinessCheck succeeded [Detail] [Expand]

️⚠️~[Staging] ServiceAPIReadinessTest: 0 Warnings warning [Detail]

API Test is not triggered due to precheck failure. Check pipeline log for details.

️❌~[Staging] SwaggerAPIView: 0 Errors, 0 Warnings failed [Detail]

️️✔️~[Staging] CadlAPIView succeeded [Detail] [Expand]

️❌ModelValidation: 14 Errors, 0 Warnings failed [Detail]

Rule	Message
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L177:22 ExampleUrl: stable/2022-01-01/examples/NetworkWatcherDelete.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L769:22 ExampleUrl: stable/2022-01-01/examples/NetworkWatcherPacketCaptureDelete.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L830:22 ExampleUrl: stable/2022-01-01/examples/NetworkWatcherPacketCaptureStop.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L1704:22 ExampleUrl: stable/2022-01-01/examples/NetworkWatcherConnectionMonitorDelete.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L1829:22 ExampleUrl: stable/2022-01-01/examples/NetworkWatcherConnectionMonitorStop.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L1890:22 ExampleUrl: stable/2022-01-01/examples/NetworkWatcherConnectionMonitorStart.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.Network/stable/2022-01-01/networkWatcher.json#L2264:22 ExampleUrl: stable/2022-01-01/examples/NetworkWatcherFlowLogDelete.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.Network/stable/2022-05-01/networkWatcher.json#L177:22 ExampleUrl: stable/2022-05-01/examples/NetworkWatcherDelete.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.Network/stable/2022-05-01/networkWatcher.json#L769:22 ExampleUrl: stable/2022-05-01/examples/NetworkWatcherPacketCaptureDelete.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.Network/stable/2022-05-01/networkWatcher.json#L830:22 ExampleUrl: stable/2022-05-01/examples/NetworkWatcherPacketCaptureStop.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.Network/stable/2022-05-01/networkWatcher.json#L1704:22 ExampleUrl: stable/2022-05-01/examples/NetworkWatcherConnectionMonitorDelete.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.Network/stable/2022-05-01/networkWatcher.json#L1829:22 ExampleUrl: stable/2022-05-01/examples/NetworkWatcherConnectionMonitorStop.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.Network/stable/2022-05-01/networkWatcher.json#L1890:22 ExampleUrl: stable/2022-05-01/examples/NetworkWatcherConnectionMonitorStart.json
`❌` LRO_RESPONSE_HEADER	Long running operation should return location or azure-AsyncOperation in header but not provided Url: Microsoft.Network/stable/2022-05-01/networkWatcher.json#L2264:22 ExampleUrl: stable/2022-05-01/examples/NetworkWatcherFlowLogDelete.json

️️✔️SemanticValidation succeeded [Detail] [Expand]

Validation passes for SemanticValidation.

️️✔️PoliCheck succeeded [Detail] [Expand]

Validation passed for PoliCheck.

️️✔️PrettierCheck succeeded [Detail] [Expand]

Validation passes for PrettierCheck.

️️✔️SpellCheck succeeded [Detail] [Expand]

Validation passes for SpellCheck.

️️✔️Lint(RPaaS) succeeded [Detail] [Expand]

Validation passes for Lint(RPaaS).

️️✔️CadlValidation succeeded [Detail] [Expand]

Validation passes for CadlValidation.

️️✔️PR Summary succeeded [Detail] [Expand]

Validation passes for Summary.

_{Posted by Swagger Pipeline | How to fix these errors?}

openapi-pipeline-app · 2023-01-20T09:39:07Z

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 failed [Detail]

❌Code Generator Failed [Logs]Release - Generate from f96293d. SDK Automation 14.0.0

warn	Skip initScript due to not configured
command	sudo apt-get install -y dotnet-sdk-6.0
command	autorest --version=2.0.4421 --csharp --reflect-api-versions --license-header=MICROSOFT_MIT_NO_VERSION [email protected]/[email protected] --csharp-sdks-folder=/mnt/vss/_work/1/s/azure-sdk-for-net/sdk ../azure-rest-api-specs/specification/network/resource-manager/readme.md
cmderr	[Autorest] realpath(): Permission denied
cmderr	[Autorest] realpath(): Permission denied
cmderr	[Autorest] realpath(): Permission denied
cmderr	[Autorest] realpath(): Permission denied
cmderr	[Autorest] realpath(): Permission denied
cmderr	[Autorest] realpath(): Permission denied

❌Microsoft.Azure.Management.Network [View full logs] [Release SDK Changes]

cmderr	[msbuild] The command could not be loaded, possibly because:
cmderr	[msbuild]   * You intended to execute a .NET application:
cmderr	[msbuild]       The application 'msbuild' does not exist.
cmderr	[msbuild]   * You intended to execute a .NET SDK command:
cmderr	[msbuild]       A compatible .NET SDK was not found.
cmderr	[msbuild] Requested SDK version: 7.0.101
cmderr	[msbuild] global.json file: /mnt/vss/_work/1/s/azure-sdk-for-net/global.json
cmderr	[msbuild] Installed SDKs:
cmderr	[msbuild] Install the [7.0.101] .NET SDK or update [/mnt/vss/_work/1/s/azure-sdk-for-net/global.json] to match an installed SDK.
cmderr	[msbuild] Learn about SDK resolution:
cmderr	[msbuild] https://aka.ms/dotnet/sdk-not-found
error	Script return with result [failed] code [145] signal [null] cwd [azure-sdk-for-net]: dotnet

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

️✔️Succeeded [Logs]Release - Generate from f96293d. 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] [Release SDK Changes]
- Azure.ResourceManager.Network.1.2.0-alpha.20230203.1.nupkg
```
info	[Changelog]
```

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

⚠️Warning [Logs]Release - Generate from f96293d. 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: 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]
cmderr	[automation_generate.sh] npm notice New major version of npm available! 8.19.3 -> 9.4.1
cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.4.1>
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] [Release SDK Changes]

info	[Changelog] ### Features Added
info	[Changelog]
info	[Changelog]   - Model NspAccessRule has a new parameter email_addresses
info	[Changelog]   - Model NspAccessRule has a new parameter phone_numbers
info	[Changelog]   - Model NspLink has a new parameter remote_perimeter_location
info	[Changelog]   - Model NspLinkReference has a new parameter remote_perimeter_location

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

⚠️Warning [Logs]Release - Generate from f96293d. 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 available: 22.3.1 -> 23.0
cmderr	[init.sh] [notice] To update, run: pip install --upgrade pip
cmderr	[init.sh] [notice] A new release of pip available: 22.3.1 -> 23.0
cmderr	[init.sh] [notice] To update, run: pip install --upgrade pip
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] [Release SDK Changes]

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

️✔️Succeeded [Logs]Release - Generate from f96293d. 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] [Release SDK Changes]

info	[Changelog] ### Features Added
info	[Changelog]
info	[Changelog] - New value `ApplicationGatewaySKUNameStandardBasic` added to type alias `ApplicationGatewaySKUName`
info	[Changelog] - New value `ApplicationGatewayTierStandardBasic` added to type alias `ApplicationGatewayTier`
info	[Changelog]
info	[Changelog] Total 0 breaking change(s), 2 additive change(s).

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

️✔️Succeeded [Logs]Release - Generate from f96293d. 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] [Release SDK Changes] Breaking Change Detected

azure-arm-network-31.0.0.tgz

info	[Changelog] **Features**
info	[Changelog]
info	[Changelog]   - Enum KnownApplicationGatewaySkuName has a new value StandardBasic
info	[Changelog]   - Enum KnownApplicationGatewayTier has a new value StandardBasic
info	[Changelog]
info	[Changelog] **Breaking Changes**
info	[Changelog]
info	[Changelog]   - Interface AdminRuleCollectionsListNextOptionalParams no longer has parameter skipToken
info	[Changelog]   - Interface AdminRuleCollectionsListNextOptionalParams no longer has parameter top
info	[Changelog]   - Interface AdminRulesListNextOptionalParams no longer has parameter skipToken
info	[Changelog]   - Interface AdminRulesListNextOptionalParams no longer has parameter top
info	[Changelog]   - Interface ConnectivityConfigurationsListNextOptionalParams no longer has parameter skipToken
info	[Changelog]   - Interface ConnectivityConfigurationsListNextOptionalParams no longer has parameter top
info	[Changelog]   - Interface ManagementGroupNetworkManagerConnectionsListNextOptionalParams no longer has parameter skipToken
info	[Changelog]   - Interface ManagementGroupNetworkManagerConnectionsListNextOptionalParams no longer has parameter top
info	[Changelog]   - Interface NetworkGroupsListNextOptionalParams no longer has parameter skipToken
info	[Changelog]   - Interface NetworkGroupsListNextOptionalParams no longer has parameter top
info	[Changelog]   - Interface NetworkInterfacesListVirtualMachineScaleSetIpConfigurationsNextOptionalParams no longer has parameter expand
info	[Changelog]   - Interface NetworkManagersListBySubscriptionNextOptionalParams no longer has parameter skipToken
info	[Changelog]   - Interface NetworkManagersListBySubscriptionNextOptionalParams no longer has parameter top
info	[Changelog]   - Interface NetworkManagersListNextOptionalParams no longer has parameter skipToken
info	[Changelog]   - Interface NetworkManagersListNextOptionalParams no longer has parameter top
info	[Changelog]   - Interface ScopeConnectionsListNextOptionalParams no longer has parameter skipToken
info	[Changelog]   - Interface ScopeConnectionsListNextOptionalParams no longer has parameter top
info	[Changelog]   - Interface SecurityAdminConfigurationsListNextOptionalParams no longer has parameter skipToken
info	[Changelog]   - Interface SecurityAdminConfigurationsListNextOptionalParams no longer has parameter top
info	[Changelog]   - Interface ServiceTagInformationListNextOptionalParams no longer has parameter noAddressPrefixes
info	[Changelog]   - Interface ServiceTagInformationListNextOptionalParams no longer has parameter tagName
info	[Changelog]   - Interface StaticMembersListNextOptionalParams no longer has parameter skipToken
info	[Changelog]   - Interface StaticMembersListNextOptionalParams no longer has parameter top
info	[Changelog]   - Interface SubscriptionNetworkManagerConnectionsListNextOptionalParams no longer has parameter skipToken
info	[Changelog]   - Interface SubscriptionNetworkManagerConnectionsListNextOptionalParams no longer has parameter top
info	[Changelog]   - Interface VirtualNetworksListDdosProtectionStatusNextOptionalParams no longer has parameter skipToken
info	[Changelog]   - Interface VirtualNetworksListDdosProtectionStatusNextOptionalParams no longer has parameter top

️🔄 azure-resource-manager-schemas inProgress [Detail]

️❌ azure-powershell failed [Detail]

❌Failed [Logs]Release - Generate from f96293d. 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 [View full logs] [Release SDK Changes]

_{Posted by Swagger Pipeline | How to fix these errors?}

openapi-pipeline-app · 2023-01-20T09:39:08Z

Generated ApiView

Language	Package Name	ApiView Link
Go	sdk/resourcemanager/network/armnetwork	https://apiview.dev/Assemblies/Review/0fafa3fbd00540e68f1afb51b188ebf5
Java	azure-resourcemanager-network-generated	https://apiview.dev/Assemblies/Review/a7e3b01a90884af98141a3ec6663bde3
.Net	Azure.ResourceManager.Network	There is no API change compared with the previous version
JavaScript	@azure/arm-network	https://apiview.dev/Assemblies/Review/ad486498eb7a4c7d95618c00dab03006

openapi-workflow-bot · 2023-01-20T09:59:49Z

Hi @supriyajha-ms, 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.
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.
If you want to know the production traffic statistic, please see ARM Traffic statistic.
If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ms/swaggerfeedback.
Note: To avoid breaking change, you can refer to Shift Left Solution for detecting breaking change in early phase at your service code repository.

openapi-workflow-bot · 2023-01-20T09:59:50Z

Hi @supriyajha-ms, Your PR has some issues. Please fix the CI sequentially by following the order of Avocado, semantic validation, model validation, breaking change, lintDiff. If you have any questions, please post your questions in this channel https://aka.ms/swaggersupport.

Task	How to fix	Priority
Avocado	Fix-Avocado	High
Semantic validation	Fix-SemanticValidation-Error	High
Model validation	Fix-ModelValidation-Error	High
LintDiff	Fix-LintDiff	high

If you need further help, please feedback via swagger feedback.

raych1 · 2023-01-21T01:59:00Z

Hi @supriyajha-ms, 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. 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. If you want to know the production traffic statistic, please see ARM Traffic statistic. If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ms/swaggerfeedback. Note: To avoid breaking change, you can refer to Shift Left Solution for detecting breaking change in early phase at your service code repository.

@supriyajha-ms , please get breaking change reviewed.

Fix runningOperationIds data type

20c3d1e

supriyajha-ms requested a review from MikhailTryakhov as a code owner January 20, 2023 09:39

openapi-assignment-bot bot assigned raych1 Jan 20, 2023

ghost added the Network label Jan 20, 2023

azure-sdk mentioned this pull request Jan 20, 2023

[AutoPR sdk/resourcemanager/network/armnetwork] Fix runningOperationIds data type azure-sdk/azure-sdk-for-go#4048

Closed

openapi-pipeline-app bot added the CI-BreakingChange-Go label Jan 20, 2023

AzureRestAPISpecReview added BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required CI-FixRequiredOnFailure resource-manager labels Jan 20, 2023

azure-sdk mentioned this pull request Jan 20, 2023

[AutoPR Microsoft.Azure.Management.Network] Fix runningOperationIds data type azure-sdk/azure-sdk-for-net#2466

Closed

Fix PR comments

d55772b

azure-sdk mentioned this pull request Jan 20, 2023

[AutoPR track2_azure-mgmt-network] Fix runningOperationIds data type azure-sdk/azure-sdk-for-python#2583

Closed

ritabanbasu approved these changes Jan 23, 2023

View reviewed changes

mikekistler added the Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 label Feb 2, 2023

raych1 added the Approved-ModelValidation label Feb 3, 2023

raych1 approved these changes Feb 3, 2023

View reviewed changes

raych1 merged commit f96293d into Azure:main Feb 3, 2023

This was referenced Feb 3, 2023

[ReleasePR sdk/resourcemanager/network/armnetwork] Release network microsoft.network official 2023 06 01 Azure/azure-sdk-for-go#19013

Closed

[ReleasePR Az.network] [network] generate with only path and body params positional Azure/azure-powershell#17956

Closed

openapi-pipeline-app bot added the CI-BreakingChange-JavaScript label Feb 3, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix runningOperationIds data type #22259

Fix runningOperationIds data type #22259

supriyajha-ms commented Jan 20, 2023 •

edited by openapi-workflow-bot bot

Loading

openapi-workflow-bot bot commented Jan 20, 2023

openapi-pipeline-app bot commented Jan 20, 2023 •

edited

Loading

openapi-pipeline-app bot commented Jan 20, 2023 •

edited

Loading

Breaking Changes Tracking

openapi-pipeline-app bot commented Jan 20, 2023 •

edited

Loading

openapi-workflow-bot bot commented Jan 20, 2023

openapi-workflow-bot bot commented Jan 20, 2023

raych1 commented Jan 21, 2023

Fix runningOperationIds data type #22259

Fix runningOperationIds data type #22259

Conversation

supriyajha-ms commented Jan 20, 2023 • edited by openapi-workflow-bot bot Loading

ARM API Information (Control Plane)

Changelog

Contribution checklist (MS Employees Only):

ARM API Review Checklist

Breaking Change Review Checklist

openapi-workflow-bot bot commented Jan 20, 2023

openapi-pipeline-app bot commented Jan 20, 2023 • edited Loading

Swagger Validation Report

openapi-pipeline-app bot commented Jan 20, 2023 • edited Loading

Swagger Generation Artifacts

Breaking Changes Tracking

openapi-pipeline-app bot commented Jan 20, 2023 • edited Loading

Generated ApiView

openapi-workflow-bot bot commented Jan 20, 2023

openapi-workflow-bot bot commented Jan 20, 2023

raych1 commented Jan 21, 2023

supriyajha-ms commented Jan 20, 2023 •

edited by openapi-workflow-bot bot

Loading

openapi-pipeline-app bot commented Jan 20, 2023 •

edited

Loading

openapi-pipeline-app bot commented Jan 20, 2023 •

edited

Loading

openapi-pipeline-app bot commented Jan 20, 2023 •

edited

Loading