Drift in dbtcloud_environment_variable when using sensitive variable DBT_ENV_SECRET_
yaeba opened this issue · comments
Describe the bug
Using dbtcloud_environment_variable
to manage sensitive variable ie DBT_ENV_SECRET_xxx
will always result in drifts, as the API response contains masked value
Error message
na
Resource configuration
resource "dbtcloud_environment_variable" "test" {
name = "DBT_ENV_SECRET_TEST"
project_id = 10
environment_values = {
"project" : "some-secret-here"
}
}
will give the following during planning
Plan: 0 to add, 1 to change, 0 to destroy.
Expected behavior
Should not result in drift
Config (please complete the following information):
- dbt Cloud provider version [e.g. 0.2.17]
Additional context
Add any other context about the problem here.
Thanks for raising this! This is a scenario I didn't think about yet.
I will try to change the behaviour and do a new release in the next days.