Updating Azure Databricks API Version to 2025-10-01-preview #9489
Conversation
|
| rule | cmd_name | rule_message | suggest_message |
|---|---|---|---|
| databricks workspace create | cmd databricks workspace create added parameter compute_mode |
||
| databricks workspace update | cmd databricks workspace update added parameter compute_mode |
|
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 pull request updates the Azure Databricks extension to use API version 2025-10-01-preview and introduces serverless compute mode support along with additional enhanced security compliance standards.
Key changes:
- Updated API version from 2024-05-01 to 2025-10-01-preview across all Databricks commands
- Added serverless compute mode support with --compute-mode parameter (Hybrid/Serverless)
- Expanded compliance standards to include HITRUST, CYBER_ESSENTIAL_PLUS, FEDRAMP_HIGH, and others
- Made managed_resource_group optional (not required for Serverless workspaces)
Reviewed changes
Copilot reviewed 33 out of 44 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| src/databricks/azext_databricks/tests/latest/test_databricks_scenario.py | Added new serverless tests and updated existing tests with hardcoded resource groups |
| src/databricks/azext_databricks/custom.py | Added logic to skip managed resource group for serverless mode |
| src/databricks/azext_databricks/aaz/latest/databricks/workspace/_create.py | Added compute_mode parameter, made managedResourceGroupId conditional, includes debug print statements |
| src/databricks/azext_databricks/aaz/latest/databricks/workspace/_update.py | Added compute_mode parameter and expanded compliance standards enum |
| src/databricks/azext_databricks/aaz/latest/databricks/workspace/_*.py | Updated API version to 2025-10-01-preview and added computeMode property |
| src/databricks/azext_databricks/aaz/latest/databricks/access_connector/_*.py | Updated API version to 2025-10-01-preview |
| src/databricks/azext_databricks/tests/latest/recordings/*.yaml | Updated test recordings with new API version and future dates |
| src/databricks/HISTORY.rst | Added 1.2.0b1 release notes |
| 'vnet_name': self.create_random_name(prefix='vnet', length=12), | ||
| 'subnet_name': self.create_random_name(prefix='subnet', length=12), | ||
| 'nsg_name': self.create_random_name(prefix='nsg', length=12), | ||
| 'resource_group_exempt': "auto-test-databricks-g9", |
There was a problem hiding this comment.
The test is using a hardcoded resource group name "auto-test-databricks-g9" instead of the dynamically generated resource group from the test decorator. This bypasses the test framework's resource cleanup mechanisms and may cause resource leaks or test conflicts. The test should use the 'rg' variable that is provided by the ResourceGroupPreparer decorator.
There was a problem hiding this comment.
These hard coded resource group names were necessary for tests in the team's subscription, due to subscription policy (the resource group has an exemption). Please let me know if there's another way to go about this testing without hardcoding an RG name!
src/databricks/azext_databricks/tests/latest/test_databricks_scenario.py
Outdated
Show resolved
Hide resolved
src/databricks/azext_databricks/aaz/latest/databricks/workspace/_create.py
Outdated
Show resolved
Hide resolved
| 'subnet_name': self.create_random_name(prefix='subnet', length=12), | ||
| 'npe_name': self.create_random_name(prefix='npe', length=12), | ||
| 'nsg_name': self.create_random_name(prefix='nsg', length=12), | ||
| 'resource_group_exempt': "auto-test-databricks-g9", |
There was a problem hiding this comment.
The test is using a hardcoded resource group name "auto-test-databricks-g9" instead of the dynamically generated resource group from the test decorator. This bypasses the test framework's resource cleanup mechanisms and may cause resource leaks or test conflicts. The test should use the 'rg' variable that is provided by the ResourceGroupPreparer decorator.
github-actions
bot
added
the
release-version-block
src/databricks/azext_databricks/aaz/latest/databricks/workspace/_create.py
Outdated
Show resolved
Hide resolved
src/databricks/azext_databricks/aaz/latest/databricks/workspace/_create.py
Outdated
Show resolved
Hide resolved
|
@microsoft-github-policy-service agree company="Microsoft" |
github-actions
bot
removed
the
release-version-block
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
4 participants
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.