Open fjakobs opened 3 months ago
The issue here has to do with the fact that this field is optional & computed. This means that the user doesn't need to specify a value for it, and in this case, the provider can define a value. A user removing the value for this then doesn't result in any plan.
Instead, this field needs to be made not computed, so that the provider can determine that the field has been removed. The server-side value could be stored elsewhere in the state to make it easily accessible if needed. Then, it will be possible to differentiate this case. This is similar to how we are dealing with databricks_share
, which has similar issues with computed attributes.
If I explicitly define the source value for a job resource and then later comment out the
source
attribute then it doesn't revert to the default value. Instead, it's always a no-op.Configuration
Expected Behavior
When I comment out the
source
attributes then the value forsource
should be the default (whatever that is).Actual Behavior
Commenting the
source
attributes has no effect. The value remains unchanged and Terraform considers this as "no change".Steps to Reproduce
terraform apply
the code abovesource
attributes`terraform apply
againTerraform and provider versions
Would you like to implement a fix?
no