Repository navigation
registered_model aliases in bundle config not applied to Unity Catalog despite successful deploy #4012
Description
Describe the issue
Model aliases defined in Databricks Asset Bundle configuration are not being applied to Unity Catalog models, even though:
- databricks bundle deploy completes successfully
- Terraform state shows aliases are configured
Configuration
Have an existing registered model in Unity Catalog with 2 versions
Create bundle configuration:
What I did:
- Model already existed in Unity Catalog with versions 1 and 2
- Used databricks bundle deployment bind to link existing model to DAB
- Ran databricks bundle deploy
- Deploy completed successfully
In UI I see a new comment and permissions were set. However, UI shows no aliases on the model.
Expected Behavior
Alias staging should be visible on the model pointing to version 2 while alias test - version 1.
Actual Behavior
Terraform state shows alias is configured, but it's not applied to the actual model in Unity Catalog.
OS and CLI version
- Databricks CLI version: 0.277.0
- Cloud: Azure
- Unity Catalog enabled
- Windows
Is this a regression?
Have tried 0.278.0, but result is the same.
Debug Logs
Output logs if you run the command with debug logs enabled. Example: databricks bundle deploy --log-level=debug. Redact if needed
{
"instances": [ { "attributes": { "aliases": [ { "alias_name": "test", "catalog_name": "", "id": "", "model_name": "", "schema_name": "", "version_num": 1 }, { "alias_name": "staging", "catalog_name": "", "id": "", "model_name": "", "schema_name": "", "version_num": 2 } ],
Activity
[-][Bug] registered_model aliases in bundle config not applied to Unity Catalog despite successful deploy[/-][+]registered_model aliases in bundle config not applied to Unity Catalog despite successful deploy[/+]varundeepsaini commentedon Dec 6, 2025
@andrewnester The Update API ignores the Aliases fields; it will require separate SetAlias/DeleteAlias calls.
Should I add calls here at the CLI level, or are you planning to support aliases in the update api itself?
varundeepsaini commentedon Dec 23, 2025
@andrewnester bump ^^
andrewnester commentedon Dec 29, 2025
@varundeepsaini I think that's fine to call SetAlias/DeleteAlias APIs in this case, but it has to be done in the TF provider. Feel free to raise a PR there and link it to the issue. Thank you!
github-actions commentedon Feb 28, 2026
This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.
SimonasS commentedon Aug 14, 2026
Requesting reopen - this was closed as stale, not fixed. The bug still reproduces on CLI v1.12.1 with the direct engine (now the default for new bundles), so deploys silently diverge from Unity Catalog in the default configuration. A fix exists (#4637), maintainer-reviewed with feedback addressed in March, awaiting final approval since. Updated repro available if useful.
jluchen commentedon Sep 16, 2026
Any movement on this? Being able to set aliases from a bundle seem like a great IaC way to manage MLFlow models.
varundeepsaini commentedon Sep 16, 2026
if this is prioritised, can just rebase and tidy up my pr