Open fishfacemcgee opened 8 months ago
We are also experiencing this issue in provider version v0.6.34.
So, what I found as a workaround is if you also set the username
attribute in the member
block, that avoids the drift. Something with the username
attribute being computed appears to be causing it to stay in a dirty state, even if neither the input nor output change between apply
executions.
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
N/A
Panic Output
N/A
Expected Behavior
Once the change has applied, no other changes will be detected as necessary without either the TF code changing or the config in OpsGenie changing.
Actual Behavior
Random drift:
Steps to Reproduce
terraform apply
to apply the original configterraform plan
to see random/unexpected driftImportant Factoids
This appears to be a full regression of #326 and/or #288.
References