Document how to resolve permadiffs caused by empty values not being set #19627
Labels
documentation
mmv1-generator
Provider-wide changes to resource templates or other generator changes
size/xs
technical-debt
Milestone
What kind of contribution is this issue about?
Other (specify in details)
Details
In some cases, the provider won't send empty values to the API, and the API will interpret that differently than the field being set to an "empty" value. This can result in "conditional" permadiffs when trying to unset a field. You can work around this with
send_empty_value
(plusallow_empty_object
for empty objects.) We should document this on the Fix a permadiff page.References
No response
The text was updated successfully, but these errors were encountered: