Remove all or none of object keys in set #818
Closed
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.
Description
These changes are meant to fix #817 issue. It is meant that all 'set' attributes are always present. If e.g. 'type' attribute is not defined in configuration, it however is stored in state as "". Whereas diff functions consider such an attribute as removed since it is changed from "" in state to nil in configuration. This behavior causes issues described in #817.
The idea is to consider an element is 'set' as removed only if all its attributes are marked as removed.
I'm not a go/tf developer, so my reasoning may be complete nonsense. At least it fixes #817.
Acceptance tests
Release Note
Release note for CHANGELOG:
References
#817
Community Note