Skip to content

Migrate Databricks from generation to main #26830

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 3 commits into from
Dec 4, 2024
Merged

Migrate Databricks from generation to main #26830

merged 3 commits into from
Dec 4, 2024

Conversation

@azure-powershell-bot
Copy link
Collaborator

@azure-powershell-bot azure-powershell-bot commented Dec 4, 2024

Description

Migrate Databricks from generation to main
The last commit of src/Databricks in generation is:
commit ef66784 Author: 徐辰 windoze@0d0a.com Date: Wed Dec 4 15:05:42 2024 +0800 Update Az.Databricks to use more intuitive parameter names for the ESC feature. (#26823) Co-authored-by: Chen Xu xuchen@microsoft.com

Checklist

  • SHOULD select appropriate branch. Cmdlets from Autorest.PowerShell should go to generation branch.
  • SHOULD make the title of PR clear and informative, and in the present imperative tense.
  • SHOULD update ChangeLog.md file(s) appropriately
    • For any service, the ChangeLog.md file can be found at 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. Add changelog in description section if PR goes into generation branch.
    • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
  • SHOULD have approved design review for the changes in this repository (Microsoft internal only) with following situations
    • Create new module from scratch
    • Create new resource types which are not easy to conform to Azure PowerShell Design Guidelines
    • Create new resource type which name doesn't use module name as prefix
    • Have design question before implementation
  • SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
  • SHOULD have proper test coverage for changes in pull request.
  • SHOULD NOT introduce breaking changes in Az minor release except preview version.
  • SHOULD NOT adjust version of module manually in pull request

@azure-client-tools-bot-prd
Copy link

azure-client-tools-bot-prd bot commented Dec 4, 2024 •
edited
Loading

️✔️Az.Accounts
️✔️Build
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Az.Compute
️✔️Build
️✔️Windows PowerShell - Windows
⚠️Az.Databricks
️✔️Build
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Breaking Change Check
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
⚠️Signature Check
⚠️PowerShell Core - Windows
Type Cmdlet Description Remediation
⚠️ Get-AzDatabricksAccessConnector Get-AzDatabricksAccessConnector Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute. Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️ Get-AzDatabricksAccessConnector Get-AzDatabricksAccessConnector changes the confirm impact. Please ensure that the change in ConfirmImpact is justified Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️ Get-AzDatabricksOutboundNetworkDependenciesEndpoint Get-AzDatabricksOutboundNetworkDependenciesEndpoint Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute. Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️ Get-AzDatabricksOutboundNetworkDependenciesEndpoint Get-AzDatabricksOutboundNetworkDependenciesEndpoint changes the confirm impact. Please ensure that the change in ConfirmImpact is justified Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️ Get-AzDatabricksVNetPeering Get-AzDatabricksVNetPeering Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute. Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️ Get-AzDatabricksVNetPeering Get-AzDatabricksVNetPeering changes the confirm impact. Please ensure that the change in ConfirmImpact is justified Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️ Get-AzDatabricksWorkspace Get-AzDatabricksWorkspace Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute. Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️ Get-AzDatabricksWorkspace Get-AzDatabricksWorkspace changes the confirm impact. Please ensure that the change in ConfirmImpact is justified Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️ New-AzDatabricksWorkspaceProviderAuthorizationObject New-AzDatabricksWorkspaceProviderAuthorizationObject changes the confirm impact. Please ensure that the change in ConfirmImpact is justified Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️Windows PowerShell - Windows
Type Cmdlet Description Remediation
⚠️ Get-AzDatabricksAccessConnector Get-AzDatabricksAccessConnector Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute. Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️ Get-AzDatabricksAccessConnector Get-AzDatabricksAccessConnector changes the confirm impact. Please ensure that the change in ConfirmImpact is justified Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️ Get-AzDatabricksOutboundNetworkDependenciesEndpoint Get-AzDatabricksOutboundNetworkDependenciesEndpoint Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute. Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️ Get-AzDatabricksOutboundNetworkDependenciesEndpoint Get-AzDatabricksOutboundNetworkDependenciesEndpoint changes the confirm impact. Please ensure that the change in ConfirmImpact is justified Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️ Get-AzDatabricksVNetPeering Get-AzDatabricksVNetPeering Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute. Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️ Get-AzDatabricksVNetPeering Get-AzDatabricksVNetPeering changes the confirm impact. Please ensure that the change in ConfirmImpact is justified Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️ Get-AzDatabricksWorkspace Get-AzDatabricksWorkspace Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute. Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️ Get-AzDatabricksWorkspace Get-AzDatabricksWorkspace changes the confirm impact. Please ensure that the change in ConfirmImpact is justified Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️ New-AzDatabricksWorkspaceProviderAuthorizationObject New-AzDatabricksWorkspaceProviderAuthorizationObject changes the confirm impact. Please ensure that the change in ConfirmImpact is justified Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
️✔️Help Example Check
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Help File Existence Check
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️File Change Check
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️UX Metadata Check
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Test
️✔️PowerShell Core - Linux
️✔️PowerShell Core - MacOS
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Az.EventHub
️✔️Build
️✔️Windows PowerShell - Windows
⚠️Az.IotHub
️✔️Build
️✔️Windows PowerShell - Windows
⚠️Test
⚠️Windows PowerShell - Windows
Type Title Current Coverage Description
⚠️ Test Coverage Less Than 50% 0.00% Test coverage for the module cannot be lower than 50%.
️✔️Az.KeyVault
️✔️Build
️✔️Windows PowerShell - Windows
️✔️Az.ManagedServiceIdentity
️✔️Build
️✔️Windows PowerShell - Windows
️✔️Az.Monitor
️✔️Build
️✔️Windows PowerShell - Windows
️✔️Az.Network
️✔️Build
️✔️Windows PowerShell - Windows
️✔️Test
️✔️Windows PowerShell - Windows
️✔️Az.OperationalInsights
️✔️Build
️✔️Windows PowerShell - Windows
️✔️Test
️✔️Windows PowerShell - Windows
️✔️Az.PrivateDns
️✔️Build
️✔️Windows PowerShell - Windows
️✔️Az.RedisCache
️✔️Build
️✔️Windows PowerShell - Windows
️✔️Test
️✔️Windows PowerShell - Windows
️✔️Az.Search
️✔️Build
️✔️Windows PowerShell - Windows
️✔️Test
️✔️Windows PowerShell - Windows
️✔️Az.Sql
️✔️Build
️✔️Windows PowerShell - Windows
⚠️Az.Storage
️✔️Build
️✔️Windows PowerShell - Windows
️✔️Breaking Change Check
️✔️Windows PowerShell - Windows
⚠️Signature Check
⚠️Windows PowerShell - Windows
Type Cmdlet Description Remediation
⚠️ Get-AzStorageAccountMigration Get-AzStorageAccountMigration Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute. Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️ Get-AzStorageAccountMigration Get-AzStorageAccountMigration changes the confirm impact. Please ensure that the change in ConfirmImpact is justified Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
️✔️Help File Existence Check
️✔️Windows PowerShell - Windows
️✔️File Change Check
️✔️Windows PowerShell - Windows
️✔️UX Metadata Check
️✔️Windows PowerShell - Windows
⚠️Test
⚠️Windows PowerShell - Windows
Type Title Current Coverage Description
⚠️ Test Coverage Less Than 50% 41.76% Test coverage for the module cannot be lower than 50%.
⚠️Az.StorageSync
️✔️Build
️✔️Windows PowerShell - Windows
⚠️Test
⚠️Windows PowerShell - Windows
Type Title Current Coverage Last Coverage Description
⚠️ Test Coverage Less Than 80% 76.00% 80.00% Test coverage cannot be lower than the number of the last release.
⚠️Az.Synapse
️✔️Build
️✔️Windows PowerShell - Windows
⚠️Test
⚠️Windows PowerShell - Windows
Type Title Current Coverage Description
⚠️ Test Coverage Less Than 50% 48.80% Test coverage for the module cannot be lower than 50%.

@VeryEarly VeryEarly self-assigned this Dec 4, 2024
@VeryEarly VeryEarly merged commit 31b4221 into main Dec 4, 2024
12 checks passed
@VeryEarly VeryEarly deleted the codegen/Databricks branch December 4, 2024 08:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@VeryEarly VeryEarly VeryEarly approved these changes

Assignees

@VeryEarly VeryEarly

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@azure-powershell-bot @VeryEarly