Revert "Updating API Version to 2026-01-01 (#9554)"

[2003LK]

This reverts commit e508767.

---

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

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

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

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).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[github-actions]

CodeGen Tools Feedback Collection

Thank 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

[github-actions]

Hi @2003LK

⚠️ Release Requirements

Module: databricks

• ⚠️ Please update VERSION to be 1.2.2 in src/databricks/setup.py

Notes

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

[Copilot]

Pull request overview

This pull request reverts a previous API version upgrade for the Azure Databricks CLI extension, rolling back from API version 2026-01-01 to 2025-10-01-preview. The revert affects the extension version, API version references across all command files, test files, and test recordings.

Changes:

• Reverts extension version from 1.2.1 back to 1.2.0 in setup.py
• Reverts API version from 2026-01-01 to 2025-10-01-preview across all databricks command files (workspace, access-connector, vnet-peering, private-endpoint-connection, private-link-resource, and outbound-endpoint commands)
• Updates test files and test recordings to reflect the reverted API version

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/setup.py	Reverts version number from 1.2.1 to 1.2.0
src/databricks/HISTORY.rst	Removes 1.2.1 changelog entry
src/databricks/azext_databricks/tests/latest/test_databricks_scenario.py	Updates tests with hardcoded resource group and removes --no-wait flags
src/databricks/azext_databricks/tests/latest/recordings/*.yaml	Updates test recordings with reverted API version and timestamps
src/databricks/azext_databricks/aaz/latest/databricks/**/*.py	Reverts API version from 2026-01-01 to 2025-10-01-preview across all command files (workspace, access_connector, vnet_peering, private_endpoint_connection, private_link_resource, outbound_endpoint)

[azclibot]

[Release] Update index.json for extension [ databricks-1.3.0 ] : https://dev.azure.com/msazure/One/_build/results?buildId=152127766&view=results