bundle/dms: set deployment display_name from bundle name on create#5406
Merged
shreyas-goenka merged 2 commits intoJun 2, 2026
Conversation
DMS-backed bundle deployments (run with `DATABRICKS_BUNDLE_MANAGED_STATE=true DATABRICKS_BUNDLE_ENGINE=direct`) never set `display_name` when creating the deployment record, so the field is stored as `null`. Populate `DisplayName` from `bundle.Config.Bundle.Name` (i.e. the `bundle.name` from `databricks.yml`) when issuing `CreateDeployment`. This matches the human-readable label users already see in `databricks bundle validate`. Existing `acceptance/bundle/dms/*` tests record the `CreateDeployment` request body via `print_requests.py`; their `output.txt` files regenerate to assert the new `display_name` field. Co-authored-by: Isaac
Co-authored-by: Isaac
shreyas-goenka
approved these changes
Jun 2, 2026
a4d2820
into
shreyas-goenka/deployment-metadata-service
21 checks passed
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
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.
Why
DMS-backed bundle deployments (run with
DATABRICKS_BUNDLE_MANAGED_STATE=true DATABRICKS_BUNDLE_ENGINE=direct) never setdisplay_namewhen creating the deployment record, so the field is stored asnull.What
Populate
DisplayNamefrombundle.Config.Bundle.Name(i.e. thebundle.namefromdatabricks.yml) when issuingCreateDeployment. This matches the human-readable label users already see indatabricks bundle validate.Tests
Existing
acceptance/bundle/dms/*tests record theCreateDeploymentrequest body viaprint_requests.py; theiroutput.txtfiles regenerate to assert the newdisplay_namefield.This pull request and its description were written by Isaac.