Add CosmosDB RP API Version 2024-09-01-preview

[carjackson-msft]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-client-tools-bot-prd]

⚠️Azure CLI Extensions Breaking Change Test

⚠️cosmosdb-preview

rule	cmd_name	rule_message	suggest_message
⚠️ 1006 - ParaAdd	cosmosdb copy create	cmd cosmosdb copy create added parameter dest_mongo_vcore
⚠️ 1009 - ParaPropRemove	cosmosdb copy create	cmd cosmosdb copy create update parameter dest_account: removed property required=True
⚠️ 1010 - ParaPropUpdate	cosmosdb create	cmd cosmosdb create update parameter server_version: updated property choices from ['3.2', '3.6', '4.0', '4.2', '5.0', '6.0'] to ['3.2', '3.6', '4.0', '4.2', '5.0', '6.0', '7.0']
⚠️ 1010 - ParaPropUpdate	cosmosdb update	cmd cosmosdb update update parameter server_version: updated property choices from ['3.2', '3.6', '4.0', '4.2', '5.0', '6.0'] to ['3.2', '3.6', '4.0', '4.2', '5.0', '6.0', '7.0']

[azure-client-tools-bot-prd]

Hi @carjackson-msft,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

DRAFT

[github-actions]

• For more info about extension versioning, please refer to Extension version schema

[evelyn-ys]

Please fix linter failure

[carjackson-msft]

Please fix linter failure

Fixed, thanks. CC: @srwshkrshnn

[evelyn-ys]

Why 1.0.1b2? There's no 1.0.1b1 before🤔

[carjackson-msft]

Hey @evelyn-ys, I had originally bumped this to 1.1.0 since we are adding a feature, but this resulted in a build error and a comment suggesting it be updated to 1.0.1b2 version.

Let me try setting it to 1.1.0 again.

[carjackson-msft]

@evelyn-ys it appears the version check is failing again, could you please let me know what the appropriate version would be if we are not setting it to the required version of 1.0.1b2?

Failing check: https://github.com/Azure/azure-cli-extensions/actions/runs/11109431994/job/30864989846?pr=7885

[carjackson-msft]

Hi @evelyn-ys, per the comment and the build failing due to this versioning, I have reverted back to the required versioning as stated in the github bot comment to allow the builds to pass. If a different version is needed (or overrides are needed) please let me or my colleague @pjohari-ms know and we can make the necessary change.

[evelyn-ys]

@AllyW Can you help with the version definition?

[AllyW]

Hi @carjackson-msft cosmos-db-preview 1.0.1 is preview version cause it has tag "azext.isPreview": true here

azure-cli-extensions/src/cosmosdb-preview/azext_cosmosdb_preview/azext_metadata.json

Line 2 in f5f8289

"azext.isPreview": true,

.

Therefore, after we have enforced new semantic versioning schema this May (https://github.com/Azure/azure-cli/blob/dev/doc/extensions/versioning_guidelines.md#versioning-of-azure-cli-extension), it takes the old release version as 1.0.1b1 and the next version would be 1.0.1b2, according to this transition table: https://github.com/Azure/azure-cli/blob/dev/doc/extensions/versioning_guidelines.md#cli-extension-version-transition-table

Since this pr actually modified cmd interfaces, 1.1.0b1 makes sense, so minor label is added here to enable 1.1.0b1 for this pr. If you have other concerns, please let me know.

[pjohari-ms]

@AllyW @evelyn-ys Update the minor versioning to 1.1.0b1 instead

[evelyn-ys]

It seems to be quite long time since PR created. Pls sync with latest cli dev branch and rerun tests again

[pjohari-ms]

@evelyn-ys Merged the PR with main, please take a look again.

[evelyn-ys]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[evelyn-ys]

@pjohari-ms I mean, you need to sync latest azure-cli repo's dev branch and run azdev setup again to reset your local env, and then you will find that current test recordings in cosmosdb extension can't work with latest cli dev. Pls rerun failed tests to fix CI

[pjohari-ms]

@evelyn-ys Thanks. Updated cli with dev branch and ran the setup again, and re recorded all tests as a precaution. Please take a look once more.

[evelyn-ys]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[pjohari-ms]

@evelyn-ys pinged you on teams chat to understand the issue - the tests are looking for wrong API version?