[DAB] Schema validation rejects `isolation_mode` in `resources.catalogs` definitions

[mauroloprete]

Describe the bug

When defining Unity Catalog resources in a databricks.yml bundle, the isolation_mode field is rejected by the CLI schema validator, even though it is a valid and documented Unity Catalog API attribute (OPEN / ISOLATED).

Steps to reproduce

Add a catalog resource with isolation_mode to your bundle:

resources:
  catalogs:
    my_catalog:
      name: "dev_application_X"
      storage_root: "abfss://dev-application-X@mystorageaccount.dfs.core.windows.net"
      isolation_mode: ISOLATED
      comment: "Catalog for X application data"
      grants:
        - principal: "my-group"
          privileges:
            - USE_CATALOG
            - USE_SCHEMA
            - SELECT

Run:

databricks bundle validate -t ENV

Expected behavior

isolation_mode: ISOLATED (or OPEN) should be accepted and applied during bundle deploy, binding the catalog to the target workspace when set to ISOLATED.

Actual behavior

The CLI rejects the field with a schema validation error, preventing the bundle from deploying catalogs with workspace-scoped isolation.

Motivation / Use case

Multi-environment bundles (dev/pre/prod) need to deploy catalogs with different isolation modes per target:

• ISOLATED in dev/pre — catalog is workspace-bound, preventing cross-workspace access during development.
• OPEN in prod — catalog is accessible across workspaces.

Without this support, isolation_mode must be set manually via the Unity Catalog UI or REST API after each deployment, breaking the IaC model that DAB is designed to provide.

CLI version

Databricks CLI v0.299.0

References

• Unity Catalog REST API: POST /api/2.1/unity-catalog/catalogs — field isolation_mode
• Unity Catalog isolation mode docs