topic Re: [DAB] registered_model aliases not being applied to Unity Catalog despite successful deploy in Data Engineering

[DAB] registered_model aliases not being applied to Unity Catalog despite successful deploy

Direo — Thu, 27 Nov 2025 07:55:25 GMT

I'm experiencing an issue with Databricks Asset Bundles where model aliases defined in the bundle configuration are not being applied to Unity Catalog, even though the deployment succeeds and the Terraform state shows the aliases are set.

Environment:

Databricks CLI version: 0.277.0
Cloud: Azure
Unity Catalog enabled

Bundle configuration:

yaml

resources:
  registered_models:
    model_name:
      name: model_name
      catalog_name: catalog      schema_name: schema      comment: comment      aliases:
        - alias_name: staging          version_num: 1
      grants:
        - privileges:
            - MANAGE          principal: USERS

What I did:

Model already existed in Unity Catalog with version 1
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 1.
Actual behavior: Terraform state shows alias is configured, but it's not applied to the actual model in Unity Catalog.

Questions:

Is this a known issue for registered_model aliases?
Is there additional configuration required for aliases (Have tried setting catalog_name, schema_name, model_name. Could not set ID)?

Re: [DAB] registered_model aliases not being applied to Unity Catalog despite successful deploy

Coffee77 — Thu, 27 Nov 2025 10:55:04 GMT

Based on this info https://docs.databricks.com/api/workspace/registeredmodels/update#aliases and https://docs.databricks.com/api/workspace/registeredmodels/create#aliases you are using correct parameters. However, this is only a guess BUT I'd say issue comes from expected content in "id" or "version_num" parameters as it seems they are used in both create and update endpoints. So, unless someone from Databricks could confirm, only new additional action to attempt in the meantime is to fill those fields and try...

Re: [DAB] registered_model aliases not being applied to Unity Catalog despite successful deploy

Direo — Thu, 27 Nov 2025 13:53:17 GMT

Thanks @Coffee77 ! Have investigated it further by trying to set aliases using Terraform. The output is the same. I have looked at terraform documentation and it turns out that it does not support alias as of now. Databricks documentations, I guess, is misleading in this case.

Re: [DAB] registered_model aliases not being applied to Unity Catalog despite successful deploy

Coffee77 — Thu, 27 Nov 2025 14:08:20 GMT

Need to wait for fixing then...

Re: [DAB] registered_model aliases not being applied to Unity Catalog despite successful deploy

iyashk-DB — Thu, 27 Nov 2025 18:52:24 GMT

Can you try by explicitly adding:

databricks model-versions get-by-alias <catalog>.<schema>.<model> staging