integration_pagerduty: fix perpetual diff in api_token #518
+747
−691
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes a perpetual diff observed in
datadog_integration_pagerduty.api_token
, when this value is unset:I called the API and realized that it is returning a redacted string even though this is unset:
So when
Read
persists this value to state, Terraform believes that it needs to remove a remotely set value.Instead, because a real value is never returned, this attribute should not be set in
Read
. This means that Terraform cannot detect drift, but if a user updates the value Terraform will still callUpdate
.Acceptance test output: