Skip to content

Add 2026-02-01-preview API version for Microsoft.DocumentDB MongoCluster#42564

Open
olivertowers wants to merge 6 commits intoAzure:mainfrom
olivertowers:olivert/mongocluster-2026-02-01-preview
Open

Add 2026-02-01-preview API version for Microsoft.DocumentDB MongoCluster#42564
olivertowers wants to merge 6 commits intoAzure:mainfrom
olivertowers:olivert/mongocluster-2026-02-01-preview

Conversation

@olivertowers
Copy link
Copy Markdown
Member

@olivertowers olivertowers commented Apr 21, 2026

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.

spec_pr_review_workflow_diagram

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.
  • A release plan has been created. If not, please create one as it will help guide you through the REST API and SDK creation process.

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.
  • For guidance on SDK breaking change review, refer to https://aka.ms/ci-fix.

- Add v2026_02_01_preview version with @previewVersion decorator
- Add networkBypassMode property to MongoClusterProperties
- Add NetworkBypassMode union type (None, AzureCosmosDB)
- Add examples and generated OpenAPI spec for 2026-02-01-preview
- Add package-2026-02-01-preview tag to readme.md
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 21, 2026

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This PR targets either the main branch of the public specs repo or the RPSaaSMaster branch of the private specs repo. These branches are not intended for iterative development. Therefore, you must acknowledge you understand that after this PR is merged, the APIs are considered shipped to Azure customers. Any further attempts at in-place modifications to the APIs will be subject to Azure's versioning and breaking change policies. Additionally, for control plane APIs, you must acknowledge that you are following all the best practices documented by ARM at aka.ms/armapibestpractices. If you do intend to release the APIs to your customers by merging this PR, add the PublishToCustomers label to your PR in acknowledgement of the above. Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).


Comment generated by summarize-checks workflow run.

@github-actions github-actions Bot added resource-manager TypeSpec Authored with TypeSpec labels Apr 21, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 21, 2026

API Change Check

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

Language API Review for Package
Swagger Microsoft.DocumentDB-MongoCluster
TypeSpec Microsoft.DocumentDB
Go sdk/resourcemanager/mongocluster/armmongocluster
Python azure-mgmt-mongocluster
JavaScript @azure/arm-mongocluster
Java com.azure.resourcemanager:azure-resourcemanager-mongocluster

Comment generated by After APIView workflow run.

@olivertowers olivertowers marked this pull request as ready for review April 21, 2026 22:33
@github-actions github-actions Bot added ARMReview new-api-version WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required ARMAutoSignedOff-IncrementalTSP ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Apr 21, 2026
- Use @SharedRoute dual-operation pattern to version the LRO
  final-state-via change: older API versions keep
  azure-async-operation, 2026-02-01-preview uses original-uri
- Add NetworkBypassMode C# clientName to client.tsp
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new 2026-02-01-preview API version for the Microsoft.DocumentDB/MongoCluster ARM spec, updating the TypeSpec source and wiring the new version into the AutoRest readme and examples.

Changes:

  • Adds package-2026-02-01-preview tag in readme.md and introduces the v2026_02_01_preview API version in TypeSpec.
  • Updates the MongoCluster TypeSpec to version-split createOrUpdate behavior and adds the new networkBypassMode property/union.
  • Adds new example payloads for the 2026-02-01-preview swagger (both generated preview/.../examples and source examples/...).

Reviewed changes

Copilot reviewed 87 out of 88 changed files in this pull request and generated 14 comments.

Show a summary per file
File Description
specification/mongocluster/resource-manager/Microsoft.DocumentDB/MongoCluster/readme.md Adds a new AutoRest tag for the 2026-02-01-preview swagger.
specification/mongocluster/resource-manager/Microsoft.DocumentDB/MongoCluster/main.tsp Adds the 2026-02-01-preview version entry marked as preview.
specification/mongocluster/resource-manager/Microsoft.DocumentDB/MongoCluster/MongoCluster.tsp Splits legacy vs new createOrUpdate behavior by version and introduces networkBypassMode.
specification/mongocluster/resource-manager/Microsoft.DocumentDB/MongoCluster/client.tsp Adds a C# client name override for the new NetworkBypassMode union.
specification/mongocluster/resource-manager/Microsoft.DocumentDB/MongoCluster/preview/2026-02-01-preview/examples/*.json Adds swagger-referenced examples for the new API version (multiple validation issues noted in comments).
specification/mongocluster/resource-manager/Microsoft.DocumentDB/MongoCluster/examples/2026-02-01-preview/*.json Adds TypeSpec source examples corresponding to the new API version.
specification/mongocluster/resource-manager/Microsoft.DocumentDB/MongoCluster/.gitignore Ignores tsp-output/ locally.

- Update suppress reason to explain legacy azure-async-operation behavior
- Fix polling URLs from api-version=2024-06-01-preview to 2026-02-01-preview
- Replace literal password values with placeholder
- Fix 'is availability' typo to 'is available' in NameAvailability example
- Remove leading '/' from type fields in all examples
- Remove subscriptionId from tenant-scoped Operations_List example
- Fix resourceGroupName inconsistency in MongoClusters_UserList (TestResourceGroup -> TestGroup)
- Add missing Azure-AsyncOperation header to PrivateEndpointConnectionDelete 202 response
@joelpineiro
Copy link
Copy Markdown
Member

joelpineiro commented Apr 22, 2026

With this version we also added storage as an optional property for GeoReplicas and PITR requests, may be worth adding those as examples, similar to specification/mongocluster/resource-manager/Microsoft.DocumentDB/MongoCluster/examples/2026-02-01-preview/MongoClusters_CreatePITR_EntraAuth.json

@joelpineiro joelpineiro self-requested a review April 22, 2026 14:43
- Add storage.type PremiumSSDv2 to GeoReplica create request and responses
- Demonstrates selecting a specific storage type when creating a geo replica
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ARMAutoSignedOff-IncrementalTSP ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review new-api-version resource-manager TypeSpec Authored with TypeSpec

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants