service/elbv2: Prevent panics with actions deleted outside Terraform #6319
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.
We will now always sort the API response by Action.Order for reading into the Terraform state. This could potentially cause a plan difference in configurations which list actions out of order so will need a note in the CHANGELOG, however this behavior seems more desirable than switching to schema.TypeSet and removing the ability to omit order from configurations.
Fixes #6171
Fixes #6256
Changes proposed in this pull request:
sortActionsBasedonTypeinTFFile()
which did not account for actions performed outside Terraform and instead sortlistener.DefaultActions
byOrder
andrule.Actions
byOrder
Previously:
Output from acceptance testing: