databricks-cli/bundle/tests/environments_override_job_c.../databricks.yml

bundle:
  name: override_job_cluster

workspace:
  host: https://acme.cloud.databricks.com/

resources:
  jobs:
    foo:
      name: job
      job_clusters:
        - job_cluster_key: key
          new_cluster:
            spark_version: 13.3.x-scala2.12

environments:
  development:
    resources:
      jobs:
        foo:
          job_clusters:
            - job_cluster_key: key
              new_cluster:
                node_type_id: i3.xlarge
                num_workers: 1

  staging:
    resources:
      jobs:
        foo:
          job_clusters:
            - job_cluster_key: key
              new_cluster:
                node_type_id: i3.2xlarge
                num_workers: 4
Renamed `environments` to `targets` in bundle configuration (#670) ## Changes Renamed Environments to Targets in bundle.yml. The change is backward-compatible and customers can continue to use `environments` in the time being. ## Tests Added tests which checks that both `environments` and `targets` sections in bundle.yml works correctly 2023-08-17 15:22:32 +00:00			`bundle:`
			`name: override_job_cluster`

			`workspace:`
			`host: https://acme.cloud.databricks.com/`

			`resources:`
			`jobs:`
			`foo:`
			`name: job`
			`job_clusters:`
			`- job_cluster_key: key`
			`new_cluster:`
			`spark_version: 13.3.x-scala2.12`

			`environments:`
			`development:`
			`resources:`
			`jobs:`
			`foo:`
			`job_clusters:`
			`- job_cluster_key: key`
			`new_cluster:`
			`node_type_id: i3.xlarge`
			`num_workers: 1`

			`staging:`
			`resources:`
			`jobs:`
			`foo:`
			`job_clusters:`
			`- job_cluster_key: key`
			`new_cluster:`
			`node_type_id: i3.2xlarge`
			`num_workers: 4`