Closed b-per closed 9 months ago
The endpoints being similar (but slightly different) to the dbt_cloud_environment_variable
resource, and different than the dbt_cloud_job
one, would it mean that we would create a new resource for those overrides?
Would calling it dbt_cloud_environment_variable_job_override
make sense?
This issue is stale because it has been open for 45 days with no activity.
This issue has been marked as Stale because it has been open for 90 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.
dbt Cloud allows overriding the environment variable values at the job level. Adding this capability would require modifying the existing
dbt_cloud_job
resource (or creating new resources?).Endpoints and payloads
I have some working code in Python but not in Go. Here are the specs for the CRUD operations.
Get
GET
"{base_url}/api/v3/accounts/{account_id}/projects/{project_id}/environment-variables/job/?job_definition_id={job_id}"
Create
POST
"{base_url}/api/v3/accounts/{account_id}/projects/{project_id}/environment-variables/"
Update
POST
"{base_url}/api/v3/accounts/{account_id}/projects/{project_id}/environment-variables/{env_var_override_id}/"
Delete
DELETE
"{base_url}/api/v3/accounts/{account_id}/projects/{project_id}/environment-variables/{env_var_override_id}/"
env_var_override_id
is theid
of the existing override (gotten from theGET
)