Fix null values in state forcing replace #311
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.
There are several comments on Upgrade v2.2.1 -> v3.4.0 forces replacement which indicate that a forced recreate occurs when there are null values in the state for certain attributes:
The attributes in question appear to be:
This PR attempts to address this issue by using a state upgrader to set each of these attributes to be non-null and to have the appropriate default value (e.g.,
0
forlower
,true
formin_lower
).