-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resource/aws_lb_listener(_rule): Allow order to be based on Terraform configuration ordering #6124
Conversation
…ly configure default_action order
…tically configure action order
Hi bflad, I was about to create an issue relating to #6119, this has broken our builds. We will pin our stuff to the previous version, but would be keen to see this go in. Thanks. |
@donbavand can you clarify what you mean by your builds are broken? Is Terraform crashing or just reporting a plan difference? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor comment but this otherwise LGTM 👍
} | ||
|
||
action { | ||
order = 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO it'd be better to flip the ordering of these (e.g. 2 then 1) to check this avoids this logic altogether?
We're not explicitly setting the rule order in terraform. During a terraform apply to an existing ALB listener, we get a validation error on the rule order. e.g
|
This has been released in version 1.41.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
The
Computed
change was just merged with #6119 😄Changes proposed in this pull request:
default_action
order
to be based on Terraform configuration orderingaction
order
to be based on Terraform configuration orderingOutput from acceptance testing: