Feature: Partial environment variables

[a-schot]

Is your feature request related to a problem? Please describe.

When provisioning environment variables through the resource dbtcloud_environment_variable, the environment already has to be deployed in order to give a value to the environment variable. When deploying dbt environments using separate state files this causes an issue where you can only really deploy the environment variables during the deployment of the last environment (eg. PROD)

Describe the solution you'd like

A dbtcloud_partial_environment_variable resource, akin to the dbtcloud_partial_license_map resource.

Describe alternatives you've considered

We are currently using count = var.environment == local.last_environment ? 1 : 0, but want a more flexible solution

Additional context

[b-per]

Thanks for raising this.

I might try to have a look in the next few days/weeks but our APIs for env variables is not the best to interact with 😄

[github-actions]

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.

[a-schot]

Hi @b-per, have you had any chance to look at this yet?

[b-per]

Hi @a-schot . No, I haven't had the time. There are a few other new resources/datasources that we want to add as well and I don't know when we will have the time to tackle this one.

[WobblyRobbly]

@a-schot I just want to clarify what you are proposing as we have a similar requirement.

As part of our CI pipeline we don't want to deploy changes to production until that part of the CI pipeline executes as a separate job. If we have 3 environments

dev, test and prod

Are you proposing that the dbtcloud_partial_environment_variable is run once for dev and test and then in a separate job with its own state file for prod , applying all prod values ?

Should the provider be able to apply single values at the project/environment/variable level instead ?