-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[CosmosDB] Support zero or more account-level capabilities #32407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
️✔️AzureCLI-FullTest
|
|
Hi @srwshkrshnn, |
|
| rule | cmd_name | rule_message | suggest_message |
|---|---|---|---|
| cosmosdb create | cmd cosmosdb create update parameter capabilities: updated property nargs from + to * |
||
| cosmosdb update | cmd cosmosdb update update parameter capabilities: updated property nargs from + to * |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR modifies the capabilities parameter for Cosmos DB account creation and updates to accept zero or more values instead of requiring at least one value.
Key Changes
- Changed
nargs='+'tonargs='*'for thecapabilitiesargument, allowing the flag to be specified without values - This aligns the parameter behavior with other clearable parameters like
assign_identityin the same file
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Related command
Description
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.