Skip to content

bundle/dms: set deployment display_name from bundle name on create#5406

Merged
shreyas-goenka merged 2 commits into
shreyas-goenka/deployment-metadata-servicefrom
pavlo-kozlov/dms-set-deployment-display-name
Jun 2, 2026
Merged

bundle/dms: set deployment display_name from bundle name on create#5406
shreyas-goenka merged 2 commits into
shreyas-goenka/deployment-metadata-servicefrom
pavlo-kozlov/dms-set-deployment-display-name

Conversation

@pavloKozlov
Copy link
Copy Markdown
Contributor

Why

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.

What

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.

Tests

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.

This pull request and its description were written by Isaac.

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
@shreyas-goenka shreyas-goenka merged commit a4d2820 into shreyas-goenka/deployment-metadata-service Jun 2, 2026
21 checks passed
@shreyas-goenka shreyas-goenka deleted the pavlo-kozlov/dms-set-deployment-display-name branch June 2, 2026 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants