resource/cloudflare_list: Do not reapply changes if only list order changed #2063
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.
Fixes #1827
Add a failing test with the example from #1827.
The test framework checks that a subsequent terraform plan does not produce a
diff. This check fails since the list is reordered on each terraform apply.
Lists are unordered so using schema.TypeList leads to spurious updates.
Use schema.TypeSet instead to avoid these.
Refactor
buildListItemsCreateRequest
to traverse the Go data structure insteadof using
resource.GetOk
. We can't easily use "item.%d.value" with TypeSetbecause its items are indexed by hash instead of position.