[cosmosdb-preview] Add support for Asynchronous DBA command for Managed Instance of Apac…

[guanzhousongmicrosoft]

Add support for Asynchronous DBA command for Managed Instance of Apache Cassandra

---

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

Related command

General Guidelines

• [x] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• [x] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• [x] 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[bot]]

Validation for Breaking Change Starting...

Thanks for your contribution!

[azure-client-tools-bot-prd[bot]]

Hi @guanzhousongmicrosoft, 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]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions[bot]]

:warning: Suggestions

Module: cosmosdb-preview

• Update version to 1.0.0b2 in setup.py
• Set azext.isPreview to true in azext_cosmosdb-preview/azext_metadata.json if not exists

Notes

• Stable/preview tag is inherited from last release. If needed, please add stable/preview label to modify it.
• Major/minor/patch/pre increment of version number is calculated by pull request code changes automatically. If needed, please add major/minor/patch/pre label to adjust it.
• For more info about extension versioning, please refer to Extension version schema