databricks-cli/integration/bundle/bundles/uc_schema/template/schema.yml.tmpl

resources:
  schemas:
    bar:
      name: test-schema-{{.unique_id}}
      catalog_name: main
      comment: This schema was created from DABs

targets:
  development:
    resources:
      pipelines:
        foo:
          target: ${resources.schemas.bar.id}
          catalog: main
Add resource for UC schemas to DABs (#1413) ## Changes This PR adds support for UC Schemas to DABs. This allows users to define schemas for tables and other assets their pipelines/workflows create as part of the DAB, thus managing the life-cycle in the DAB. The first version has a couple of intentional limitations: 1. The owner of the schema will be the deployment user. Changing the owner of the schema is not allowed (yet). `run_as` will not be restricted for DABs containing UC schemas. Let's limit the scope of run_as to the compute identity used instead of ownership of data assets like UC schemas. 2. API fields that are present in the update API but not the create API. For example: enabling predictive optimization is not supported in the create schema API and thus is not available in DABs at the moment. ## Tests Manually and integration test. Manually verified the following work: 1. Development mode adds a "dev_" prefix. 2. Modified status is correctly computed in the `bundle summary` command. 3. Grants work as expected, for assigning privileges. 4. Variable interpolation works for the schema ID. 2024-07-31 12:16:28 +00:00			`resources:`
			`schemas:`
			`bar:`
			`name: test-schema-{{.unique_id}}`
			`catalog_name: main`
			`comment: This schema was created from DABs`

			`targets:`
			`development:`
			`resources:`
			`pipelines:`
			`foo:`
			`target: ${resources.schemas.bar.id}`
Fixed TestAccBundleDeployUcSchema test (#1997) ## Changes It was failing because when schema.yml was removed, `catalog: main` option left set in the base pipeline definition in databricks.yml which lead to incorrect config (empty target schema) https://github.com/databricks/cli/pull/1413 Backend behaviour changed and DLT pipelines stopped to accept empty targets leading to the error which was ignored before. ## Tests ``` --- PASS: TestAccBundleDeployUcSchema (41.75s) PASS coverage: 33.3% of statements in ./... ok github.com/databricks/cli/internal/bundle 42.210s coverage: 33.3% of statements in ./... ``` 2024-12-11 14:00:43 +00:00			`catalog: main`