resource/aws_lb_listener(_rule): Set action order to Computed #6119
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 #6116
While the acceptance testing is not finding this scenario, the order value may return as
1
. This may be caused by web console updates. We should not default this to1
as that could cause0
to1
plan differences and shying away from a stopgapDiffSuppressFunc
here because we may make this configuration based on theTypeList
index in the future if its undefined.Changes proposed in this pull request:
default_action
order
toComputed
action
order
toComputed
Output from acceptance testing: