You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[#232](https://github.com/dbt-labs/terraform-provider-dbtcloud/issues/232) add deprecation notice for `dbtcloud_project_artefacts` as the resource is not required now that dbt Explorer is GA.
12
+
-[#208](https://github.com/dbt-labs/terraform-provider-dbtcloud/issues/208) add new `dbtcloud_partial_license_map` for defining SSO group mapping to license types from different Terraform projects/resources
-`deferring_job_id` (Number) Job identifier that this job defers to (legacy deferring approach)
120
120
-`description` (String) Description for the job
121
121
-`generate_docs` (Boolean) Flag for whether the job should generate documentation
122
-
-`is_active` (Boolean) Flag for whether the job is marked active or deleted. To create/keep a job in a 'deactivated' state, check the `triggers` config.
122
+
-`is_active` (Boolean) Should always be set to true as setting it to false is the same as creating a job in a deleted state. To create/keep a job in a 'deactivated' state, check the `triggers` config.
123
123
-`job_completion_trigger_condition` (Block Set, Max: 1) Which other job should trigger this job when it finishes, and on which conditions (sometimes referred as 'job chaining'). (see [below for nested schema](#nestedblock--job_completion_trigger_condition))
124
124
-`num_threads` (Number) Number of threads to use in the job
125
125
-`run_generate_sources` (Boolean) Flag for whether the job should add a `dbt source freshness` step to the job. The difference between manually adding a step with `dbt source freshness` in the job steps or using this flag is that with this flag, a failed freshness will still allow the following steps to run.
Set up partial license maps with only a subset of SSO groups for a given license type.
6
+
This resource is different from dbtcloud_license_map as it allows having different resources setting up different groups for the same license type.
7
+
If a company uses only one Terraform project/workspace to manage all their dbt Cloud Account config, it is recommended to use dbt_cloud_license_map instead of dbt_cloud_group_partial_license_map.
8
+
~> This is a new resource like other "partial" ones and any feedback is welcome in the GitHub repository.
9
+
---
10
+
11
+
# dbtcloud_partial_license_map (Resource)
12
+
13
+
14
+
Set up partial license maps with only a subset of SSO groups for a given license type.
15
+
16
+
This resource is different from `dbtcloud_license_map` as it allows having different resources setting up different groups for the same license type.
17
+
18
+
If a company uses only one Terraform project/workspace to manage all their dbt Cloud Account config, it is recommended to use `dbt_cloud_license_map` instead of `dbt_cloud_group_partial_license_map`.
19
+
20
+
~> This is a new resource like other "partial" ones and any feedback is welcome in the GitHub repository.
[Deprecated] Resource for mentioning what jobs are the source of truth for the legacy dbt Docs and dbt Source Freshness pages. dbt Explorer doesn't require this config anymore.
6
6
---
7
7
8
8
# dbtcloud_project_artefacts (Resource)
9
9
10
10
11
-
11
+
[Deprecated] Resource for mentioning what jobs are the source of truth for the legacy dbt Docs and dbt Source Freshness pages. dbt Explorer doesn't require this config anymore.
0 commit comments