AGC-v.2025-01-01

[cdxu-147]

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.

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 created in adherence to OpenAPI specs PR creation guidance).
• 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.
• Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
• 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.
• If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
• 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 ARM review (PR workflow diagram Step 2), 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.

[openapi-pipeline-app]

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

[openapi-pipeline-app]

Generated ApiView

Language	Package Name	ApiView Link
Go	sdk/resourcemanager/servicenetworking/armservicenetworking	There is no API change compared with the previous version
JavaScript	@azure/arm-servicenetworking	https://apiview.dev/Assemblies/Review/78fd700d950f45129790c97f9171efdc?revisionId=a19d394848f240a89e44b40ef4ea033e
Python	azure-mgmt-servicenetworking	https://apiview.dev/Assemblies/Review/eaf5055b29fb4fdeb0e50b2f132f6bb2?revisionId=9a06402e1cef4427a6eaa5c6b2a8d317
TypeSpec	ServiceNetworking.Management	https://apiview.dev/Assemblies/Review/8e192291c45643238e598a06eac03d95?revisionId=6ae7abe9f1a54140b177afff88e5cc24

[azure-sdk]

API change check

APIView has identified API level changes in this PR and created following API reviews.

Microsoft.ServiceNetworking
Microsoft.ServiceNetworking

[rkmanda]

What are the changes here other than changing the API version string?

[rkmanda]

[cdxu-147]

What are the changes here other than changing the API version string?

There's no other change, just releasing a stable version same as the preview version

[msyyc]

Python SDK could be generated from Typespec so there is no need to keep configuration for swagger.

[cdxu-147]

Thanks for reviewing @msyyc , can you please also add the BreakingChange-JavaScript-Sdk-Approved label to help us complete this PR? Thanks

[msyyc]

Add JS Owner @kazrael2119 for JS SDK review.

[qiaozha]

@msyyc have we decided to release from typespec for this service?

[msyyc]

Python doesn't see any blocker and I don't want pipeline to generate SDK twice from swagger and typespec which is waste of pipeline resources.