Skip to content

Upgrade API version to 2026-01-01#29167

Open
2003LK wants to merge 10 commits intoAzure:mainfrom
2003LK:api-update-1-2026
Open

Upgrade API version to 2026-01-01#29167
2003LK wants to merge 10 commits intoAzure:mainfrom
2003LK:api-update-1-2026

Conversation

@2003LK
Copy link

@2003LK 2003LK commented Feb 12, 2026

Description

Mandatory Checklist

  • SHOULD update ChangeLog.md file(s) appropriately
    • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
      • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
    • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
  • SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
  • SHOULD have proper test coverage for changes in pull request.
  • SHOULD NOT adjust version of module manually in pull request

Copilot AI review requested due to automatic review settings February 12, 2026 04:18
@azure-client-tools-bot-prd
Copy link

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

Copy link
Contributor

Copilot AI left a 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 pull request upgrades the Azure Databricks PowerShell module from API version 2024-05-01 to 2026-01-01. The primary functional change is the addition of a new ComputeMode parameter to the New-AzDatabricksWorkspace cmdlet, which allows users to specify 'Hybrid' or 'Serverless' compute modes when creating workspaces.

Changes:

  • API version upgraded from 2024-05-01 to 2026-01-01 across all module components
  • Added ComputeMode parameter (Hybrid/Serverless) to workspace creation
  • Updated all API model references from Api20240501 to Api202601
  • Enhanced test coverage with new scenarios for Serverless and Enhanced Security Compliance (ESC) workspaces
  • Updated test infrastructure with second resource group and cleanup logic

Reviewed changes

Copilot reviewed 30 out of 32 changed files in this pull request and generated 5 comments.

Show a summary per file
File Description
src/Databricks/Databricks/ChangeLog.md Added entry for ComputeMode parameter support
src/Databricks/Databricks/help/New-AzDatabricksWorkspace.md Added documentation for ComputeMode parameter
src/Databricks/Databricks.Autorest/README.md Updated API version commit hash and module version
src/Databricks/Databricks.Autorest/custom/New-AzDatabricksWorkspace.ps1 Implemented ComputeMode logic with default to 'Hybrid'
src/Databricks/Databricks.Autorest/custom/Update-AzDatabricksWorkspace.ps1 Updated API model references and breaking change attributes
src/Databricks/Databricks.Autorest/custom/Update-AzDatabricksVNetPeering.ps1 Updated API model references
src/Databricks/Databricks.Autorest/custom/New-AzDatabricksWorkspaceProviderAuthorizationObject.ps1 Updated API model references
src/Databricks/Databricks.Autorest/test/AzDatabricksWorkspace.Tests.ps1 Added Serverless and ESC test scenarios, commented out OutboundNetworkDependencies test
src/Databricks/Databricks.Autorest/test/AzDatabricksVNetPeering.Tests.ps1 Added -NoWait to cleanup operation
src/Databricks/Databricks.Autorest/test/utils.ps1 Added second resource group setup and enabled cleanup
src/Databricks/Databricks.Autorest/test/env.json, localEnv.json Added test environment variables
src/Databricks/Databricks.Autorest/test/AzDatabricksVNetPeering.Recording.json Updated test recordings with new API version
src/Databricks/Databricks.Autorest/Properties/AssemblyInfo.cs Updated assembly version (though inconsistent with README)
src/Databricks/Databricks.Autorest/docs/*.md Updated all help documentation with new API model references
src/Databricks/Databricks.Autorest/UX/*.json Updated API versions in UX configuration
src/Databricks/Databricks.Autorest/generate-info.json Deleted (normal for regeneration)

@isra-fel
Copy link
Member

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@isra-fel
Copy link
Member

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

Copilot AI review requested due to automatic review settings February 18, 2026 02:17
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 47 out of 49 changed files in this pull request and generated 6 comments.

@2003LK 2003LK marked this pull request as ready for review February 18, 2026 02:25
Copilot AI review requested due to automatic review settings February 18, 2026 02:25
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 46 out of 48 changed files in this pull request and generated 2 comments.

Comment on lines 20 to 23
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Databricks", "Databricks\Databricks.csproj", "{78057EB6-1C85-4118-94B4-8021CCD6902E}"
EndProject
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Databricks.Autorest", "Databricks.Autorest", "{5FE84A12-8651-7F44-066E-17161CDB0E9D}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Az.Databricks", "..\..\generated\Databricks\Databricks.Autorest\Az.Databricks.csproj", "{2B4B9E93-9F35-499A-905E-1DA5210E71A7}"
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Az.Databricks", "Databricks.Autorest\Az.Databricks.csproj", "{CD4F8633-C856-4A59-808E-8B50705F6E26}"
EndProject
Copy link

Copilot AI Feb 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The solution now references Databricks.Autorest\Az.Databricks.csproj, but there is no Az.Databricks.csproj under src/Databricks/Databricks.Autorest/ in the repo. This will break opening/building the Databricks solution. Update the path to the actual project location (currently under generated/Databricks/Databricks.Autorest/) or add/move the csproj so the reference resolves.

Copilot uses AI. Check for mistakes.
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@isra-fel Is this an issue? This isn't something I changed manually

@isra-fel
Copy link
Member

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

Copy link
Member

@isra-fel isra-fel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please see my comments inline. Thanks


```yaml
Type: Microsoft.Azure.PowerShell.Cmdlets.Databricks.Support.ComplianceStandard[]
Type: System.String[]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This breaking change (Enum to string) should have been part of autorest.powershell v4 but Databricks is actually still on v3. I don't understand why. @VeryEarly what's your opinion here?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't want to update to autorest v4 yet, will do after this PR.

@github-actions
Copy link

This PR was labeled "needs-revision" because it has unresolved review comments or CI failures.
Please resolve all open review comments and make sure all CI checks are green. Refer to our guide to troubleshoot common CI failures.

Copilot AI review requested due to automatic review settings February 19, 2026 21:26
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 46 out of 48 changed files in this pull request and generated 4 comments.

[OutputType([Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.Api20240501.IWorkspace])]
[Microsoft.Azure.PowerShell.Cmdlets.Databricks.Runtime.OutputBreakingChangeAttribute("Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.Api20240501.IWorkspace", "16.0.0", "2.0.0", "May 2026", ReplacementCmdletOutputType = "Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.IWorkspace", DeprecatedOutputProperties = ("PrivateEndpointConnection, ComplianceSecurityProfileComplianceStandard, Authorization"), NewOutputProperties = ("PrivateEndpointConnection, ComplianceSecurityProfileComplianceStandard, Authorization The types of the properties will be changed from object to 'List'"))]
[OutputType([Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.Api202601.IWorkspace])]
[Microsoft.Azure.PowerShell.Cmdlets.Databricks.Runtime.OutputBreakingChangeAttribute("Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.Api202601.IWorkspace", "16.0.0", "2.0.0", "May 2026", ReplacementCmdletOutputType = "Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.IWorkspace", DeprecatedOutputProperties = ("PrivateEndpointConnection, ComplianceSecurityProfileComplianceStandard, Authorization"), NewOutputProperties = ("PrivateEndpointConnection, ComplianceSecurityProfileComplianceStandard, Authorization The types of the properties will be changed from object to 'List'"))]
Copy link

Copilot AI Feb 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The breaking change date format "May 2026" does not follow the required "YYYY/MM/DD" format. According to repository conventions, breaking change attributes should use a specific date format like "2026/05/01" rather than text-based formats like "May 2026". This format is required for automated processing of breaking change announcements.

Copilot generated this review using guidance from repository custom instructions.
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change was done by the powershell team

[OutputType([Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.Api20240501.IWorkspace])]
[Microsoft.Azure.PowerShell.Cmdlets.Databricks.Runtime.OutputBreakingChangeAttribute("Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.Api20240501.IWorkspace", "16.0.0", "2.0.0", "May 2026", ReplacementCmdletOutputType = "Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.IWorkspace", DeprecatedOutputProperties = ("PrivateEndpointConnection, ComplianceSecurityProfileComplianceStandard, Authorization"), NewOutputProperties = ("PrivateEndpointConnection, ComplianceSecurityProfileComplianceStandard, Authorization The types of the properties will be changed from object to 'List'"))]
[OutputType([Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.Api202601.IWorkspace])]
[Microsoft.Azure.PowerShell.Cmdlets.Databricks.Runtime.OutputBreakingChangeAttribute("Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.Api202601.IWorkspace", "16.0.0", "2.0.0", "May 2026", ReplacementCmdletOutputType = "Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.IWorkspace", DeprecatedOutputProperties = ("PrivateEndpointConnection, ComplianceSecurityProfileComplianceStandard, Authorization"), NewOutputProperties = ("PrivateEndpointConnection, ComplianceSecurityProfileComplianceStandard, Authorization The types of the properties will be changed from object to 'List'"))]
Copy link

Copilot AI Feb 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The breaking change date format "May 2026" does not follow the required "YYYY/MM/DD" format. According to repository conventions, breaking change attributes should use a specific date format like "2026/05/01" rather than text-based formats like "May 2026". This format is required for automated processing of breaking change announcements.

Copilot generated this review using guidance from repository custom instructions.
[OutputType([Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.Api20240501.IVirtualNetworkPeering])]
[Microsoft.Azure.PowerShell.Cmdlets.Databricks.Runtime.OutputBreakingChangeAttribute("Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.Api20240501.IVirtualNetworkPeering", "16.0.0", "2.0.0", "May 2026", ReplacementCmdletOutputType = "Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.IVirtualNetworkPeering", DeprecatedOutputProperties = ("DatabrickAddressSpaceAddressPrefix, RemoteAddressSpaceAddressPrefix 'System.String[]'"), NewOutputProperties = ("DatabrickAddressSpaceAddressPrefix, RemoteAddressSpaceAddressPrefix 'System.Collections.Generic.List`1[System.String]'"))]
[OutputType([Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.Api202601.IVirtualNetworkPeering])]
[Microsoft.Azure.PowerShell.Cmdlets.Databricks.Runtime.OutputBreakingChangeAttribute("Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.Api202601.IVirtualNetworkPeering", "16.0.0", "2.0.0", "May 2026", ReplacementCmdletOutputType = "Microsoft.Azure.PowerShell.Cmdlets.Databricks.Models.IVirtualNetworkPeering", DeprecatedOutputProperties = ("DatabrickAddressSpaceAddressPrefix, RemoteAddressSpaceAddressPrefix 'System.String[]'"), NewOutputProperties = ("DatabrickAddressSpaceAddressPrefix, RemoteAddressSpaceAddressPrefix 'System.Collections.Generic.List`1[System.String]'"))]
Copy link

Copilot AI Feb 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The breaking change date format "May 2026" does not follow the required "YYYY/MM/DD" format. According to repository conventions, breaking change attributes should use a specific date format like "2026/05/01" rather than text-based formats like "May 2026". This format is required for automated processing of breaking change announcements.

Copilot generated this review using guidance from repository custom instructions.
@isra-fel
Copy link
Member

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@isra-fel
Copy link
Member

/azp run

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments