Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document how to resolve permadiffs caused by empty values not being set #19627

Open
melinath opened this issue Sep 25, 2024 · 0 comments
Open

Document how to resolve permadiffs caused by empty values not being set #19627

melinath opened this issue Sep 25, 2024 · 0 comments
Labels
documentation mmv1-generator Provider-wide changes to resource templates or other generator changes size/xs technical-debt
Milestone
Goals

Comments

@melinath
Copy link
Collaborator

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 (plus allow_empty_object for empty objects.) We should document this on the Fix a permadiff page.

References

No response
@melinath melinath added documentation technical-debt mmv1-generator Provider-wide changes to resource templates or other generator changes labels Sep 25, 2024
@BBBmau BBBmau added the size/xs label Oct 21, 2024
@BBBmau BBBmau added this to the Goals milestone Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation mmv1-generator Provider-wide changes to resource templates or other generator changes size/xs technical-debt
Projects
None yet
Milestone
Goals
Development

No branches or pull requests
2 participants
@melinath @BBBmau