Repository navigation
direct: add a Bind plan action - #7110
Draft
shreyas-goenka wants to merge 1 commit into
Draft
shreyas-goenka wants to merge 1 commit into
shreyas-goenka wants to merge 1 commit into
Conversation
CalculatePlan can now adopt an existing workspace resource: when DeploymentBundle.BindKey names a resource, it is read by BindID instead of its state entry and planned as Bind. Apply records it in state without an API write, taking the id from the plan entry because the resource is not in state yet; the next deploy applies any config differences. Nothing sets BindKey yet; DMS bind uses it in a follow-up. Co-authored-by: Isaac <no-reply@databricks.com>
shreyas-goenka
added this pull request to stack #7114
October 19, 2026 15:52
Collaborator
Integration test reportCommit: 8afba87
Top 6 slowest tests (at least 2 minutes):
|
This branch has not been deployed
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
2 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
Adds a
Bindplan action to the direct engine. WhenDeploymentBundle.BindKeynames a resource,CalculatePlanreads it byBindIDinstead of its state entry and plansBind; apply records it in state with no API call (the next deploy applies config differences). A bound resource's${...id}resolves from its plan entry.Why
First step of moving
bundle deployment bindonto a planned action, so the same flow can record a bind with the deployment metadata service. Nothing setsBindKeyyet.Tests
Unit test for the id lookup; existing suites unchanged.
This pull request and its description were written by Isaac.