-
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
r/aws_lb_listener_certificate: remove from state if listener not found #32412
r/aws_lb_listener_certificate: remove from state if listener not found #32412
Conversation
Community NoteVoting for Prioritization
For Submitters
|
add changelog
a734e5d
to
7fa221a
Compare
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.
LGTM 🎉
% make testacc PKG=elbv2 TESTS=TestAccELBV2ListenerCertificate_
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/elbv2/... -v -count 1 -parallel 20 -run='TestAccELBV2ListenerCertificate_' -timeout 180m
--- PASS: TestAccELBV2ListenerCertificate_disappears (150.33s)
--- PASS: TestAccELBV2ListenerCertificate_basic (164.35s)
--- PASS: TestAccELBV2ListenerCertificate_CertificateARN_underscores (164.48s)
--- PASS: TestAccELBV2ListenerCertificate_disappears_Listener (169.53s)
--- PASS: TestAccELBV2ListenerCertificate_multiple (225.41s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/elbv2 228.940s
Thanks for your contribution, @lomluca! 👏 |
This functionality has been released in v5.13.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
Currently, if the listener (or the Load Balancer) has been removed by an external actor, the plan does not work due to "ListenerNotFound" error by AWS API.
The correct behaviour is that the resource is removed from state, and it will be eventually created again if it is still in the configuration.
Relations
Closes #30489