bundle migrate: handle added/removed resources gracefully#5463
Merged
Conversation
Collaborator
|
Commit: 1ad2f9d
27 interesting tests: 15 SKIP, 7 KNOWN, 5 flaky
Top 28 slowest tests (at least 2 minutes):
|
denik
force-pushed
the
denik/migration-added-removed
branch
from
1117995 to
fe0d059
Compare
denik
force-pushed
the
denik/migration-added-removed
branch
from
fe0d059 to
b4d3e40
Compare
denik
force-pushed
the
denik/migration-added-removed
branch
from
b4d3e40 to
7bf336c
Compare
denik
force-pushed
the
denik/migration-added-removed
branch
from
7bf336c to
f7c3b39
Compare
denik
force-pushed
the
denik/migration-added-removed
branch
from
f7c3b39 to
f9b0ae3
Compare
Resources in databricks.yml but not in terraform state (added since last deploy) are now skipped during migration and will be created on the first direct deploy, instead of failing the migration. Resources in terraform state but not in databricks.yml (removed since last deploy) now have their ID preserved in the direct state so the next direct deploy will plan and execute deletion, instead of failing the migration. Co-authored-by: Isaac
denik
force-pushed
the
denik/migration-added-removed
branch
from
f9b0ae3 to
bb2f595
Compare
pietern
approved these changes
Jun 8, 2026
pietern
left a comment
pietern
left a comment
Contributor
There was a problem hiding this comment.
How does this mesh with automigration?
Contributor
Author
This directly enables auto-migration by not requiring a prior deploy. (Although we might still choose to auto-migration after terraform deployment while we still have terraform implementation in). |
deco-sdk-tagging Bot
added a commit
that referenced
this pull request
Jun 10, 2026
## Release v1.3.0 ### Notable Changes * The `direct` deployment engine is now Generally Available and the default for new deployments. To opt out, set `engine: terraform` under `bundle` in your `databricks.yml` or set `DATABRICKS_BUNDLE_ENGINE=terraform`. Existing deployments keep their current engine; see https://docs.databricks.com/aws/en/dev-tools/bundles/direct to migrate. ### CLI * Added the `databricks quickstart` command, a short introduction to the CLI that prints a human-friendly guide interactively and an agent-oriented version when run non-interactively ([#5464](#5464)). * Add `databricks version --check` to report whether a newer CLI version is available and print the upgrade command for the detected install method ([#5469](#5469)). * `databricks auth describe` now verifies credentials against both the workspace and account endpoints before reporting a failure, fixing false "Unable to authenticate" errors for account console profiles ([#5479](#5479)). * `databricks auth login` no longer prompts for workspace selection when logging in to an account console host (`https://accounts.*`). Pass `--workspace-id` explicitly to store a workspace ID on such a profile ([#5504](#5504)). * `databricks auth profiles --skip-validate` no longer makes any network calls; the host metadata fetch is skipped along with validation ([#5530](#5530)). ### Bundles * Set the default `data_security_mode` to `DATA_SECURITY_MODE_AUTO` in bundle templates ([#5452](#5452)). * Mark vector search index index_subtype as backend_default to prevent drift after deployment ([#5454](#5454)). * `bundle deployment migrate`: handle resources added to or removed from `databricks.yml` since the last Terraform deploy ([#5463](#5463)). * Add the `genie_spaces` bundle resource for managing Databricks Genie spaces as code, plus `bundle generate genie-space` to import an existing space. Direct deployment engine only ([#5282](#5282)). * Fix spurious recreate of schemas and volumes whose names use mixed case ([#5531](#5531)).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Why
Towards auto-migration: we should migrate any situation without errors.
Tests
New acceptance tests.