[Microsoft.DocumentDB] Cosmos DB 2025-05-01-preview API version release.

[pjohari-ms]

Description

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • For SDK-based development mode, update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • For autorest-based development mode, include the changelog in the PR description.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[pjohari-ms]

@wyunchi-ms @dolauli Can the pipelines be run again?

[pjohari-ms]

/azp run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 27658 in repo Azure/azure-powershell

[wyunchi-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[pjohari-ms]

@wyunchi-ms I have regenerated the SDK, not sure why I needed to do that. The tests are passing in the previous build, can you restart the pipelines?

[wyunchi-ms]

/azp run

[wyunchi-ms]

There are too many changed files in this PR. Could you please split this PR into some smaller PRs?

[pjohari-ms]

@wyunchi-ms Per our previous discussions with powershell team, they suggested we sync with main everytime we create a new powershell PR for release. We followed the same process. Is this not expected?

[msJinLei]

@wyunchi-ms Per our previous discussions with powershell team, they suggested we sync with main everytime we create a new powershell PR for release. We followed the same process. Is this not expected?

@pjohari-ms The PR is too large to review. Please split the PR into syncup-with-main PR and API-update PR, thanks

[github-actions]

This PR was labeled "needs-revision" because it has unresolved review comments or CI failures.
Please resolve all open review comments and make sure all CI checks are green. Refer to our guide to troubleshoot common CI failures.