Updating API Version to 2026-01-01#9554
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
|
Hi @2003LK, |
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
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>
|
CodeGen Tools Feedback CollectionThank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey |
|
There was a problem hiding this comment.
Pull request overview
This PR updates the Azure Databricks extension API version from 2025-10-01-preview to 2026-01-01, moving from a preview API version to a stable release version. The changes include updates to the API version string across all command modules and regenerated test recordings.
Changes:
- Updated API version from
2025-10-01-previewto2026-01-01across all databricks commands - Updated test scenarios to use resource group parameter consistently
- Added
--no-waitflag to vnet-peering delete commands in tests - Updated HISTORY.rst with version 1.3.0 release notes
- Regenerated all test recordings with the new API version
Reviewed changes
Copilot reviewed 32 out of 43 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| HISTORY.rst | Added version 1.3.0 with API version upgrade notes |
| test_databricks_scenario.py | Fixed resource group references and added --no-wait to vnet-peering delete commands |
| aaz/latest/databricks/workspace/*.py | Updated API version strings for workspace commands |
| aaz/latest/databricks/access_connector/*.py | Updated API version strings for access connector commands |
| aaz/latest/databricks/workspace/vnet_peering/*.py | Updated API version strings for vnet peering commands |
| aaz/latest/databricks/workspace/private_endpoint_connection/*.py | Updated API version strings for private endpoint connection commands |
| aaz/latest/databricks/workspace/private_link_resource/*.py | Updated API version strings for private link resource commands |
| aaz/latest/databricks/workspace/outbound_endpoint/*.py | Updated API version strings for outbound endpoint commands |
| test_*.yaml | Regenerated test recordings with new API version and updated timestamps |
| self.check('peeringState', 'Initiated') | ||
| ]) | ||
| self.cmd('az databricks workspace vnet-peering delete -n {peering_name} --workspace-name {workspace_name} -g {rg}') | ||
| self.cmd('az databricks workspace vnet-peering delete -n {peering_name} --workspace-name {workspace_name} -g {rg} --no-wait true') |
There was a problem hiding this comment.
The --no-wait flag should not have a value. In Azure CLI, --no-wait is a boolean flag that should be used without any arguments. Change --no-wait true to just --no-wait.
|
|
||
| # delete the peering | ||
| self.cmd('az databricks workspace vnet-peering delete -n {peering_name} --workspace-name {workspace_name} -g {rg}') | ||
| self.cmd('az databricks workspace vnet-peering delete -n {peering_name} --workspace-name {workspace_name} -g {rg} --no-wait true') |
There was a problem hiding this comment.
The --no-wait flag should not have a value. In Azure CLI, --no-wait is a boolean flag that should be used without any arguments. Change --no-wait true to just --no-wait.
please update the version in |
|
@2003LK plz provide the link of pr in Azure/aaz, thanks. |
I didn't use aaz-dev-tools to update command models so I didn't touch Azure/aaz |
|
@2003LK we should do that - update the metadata https://github.com/Azure/aaz/tree/main/Commands/databricks via codegen tool. otherwise, all changes will be overwritten next time due to we modified the generated files. |
Created this PR: Azure/aaz#933 |
|
[Release] Update index.json for extension [ databricks-1.2.1 ] : https://dev.azure.com/msazure/One/_build/results?buildId=151769004&view=results |
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install wheel==0.30.0required)For new extensions:
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.jsonautomatically.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.