Declarative Automation Bundles Volume creation fails with CATALOG_DOES_NOT_EXIST on first deploy

Luisbct
New Contributor II

Hi everyone,

I'm working with DAB, and I'm running into a deployment ordering issue.

On my first deploy, I get this error:

Error: cannot create resources.volumes.raw_data: Catalog 'mycatalog_prod' does not exist. (404 CATALOG_DOES_NOT_EXIST)

Endpoint: POST /api/2.1/unity-catalog/volumes
HTTP Status: 404 Not Found

But all the other resources (catalog,external locations, schemas) are created without problems.

However, when I run the exact same command a second time:

DATABRICKS_BUNDLE_ENGINE=direct databricks bundle deploy

it succeeds without any errors.

I have my resources split in multiple yml files:

  • catalog.yml
  • external_locations.yml
  • schemas.yml
  • volumes.yml

My Volumen resource is like

resources:
  volumes:
    raw_data:
      catalog_name: ${var.catalog}
      name: raw_data
      schema_name: staging
      volume_type: EXTERNAL
      storage_location: abfss://staging@stdatatest.dfs.core.windows.net/data/
      grants:
        - principal: mygroup
          privileges:
             - MANAGE

I tried change the ${var.catalog} to "mycatalog_prod" but didn't work 

Is this expected behavior due to resource creation order in DAB?