Closed Dave-EMIS closed 4 weeks ago
Voting for Prioritization
Volunteering to Work on This Issue
I'm not going to raise a PR, but I think the issue is a missing return
on line 101:
Without a return
it carries on expecting output.TrustStoreRevocations[0]
to be there on 104 and crashes.
[!WARNING] This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.
Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.
This functionality has been released in v5.62.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!
Terraform Core Version
1.8.2
AWS Provider Version
5.56.1
Affected Resource(s)
aws_lb_trust_store_revocation
Expected Behavior
AWS Error returned to the consumer to know about the problem and that they need to correct their CRL.
Actual Behavior
Crashes
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Attempting to create the resource via
The S3 bucket, object and trust store already exist.
Steps to Reproduce
Use an invalid format CRL file in the S3 bucket and then
terraform apply
.As is seen in the debug logs (below) there was an error returned from AWS, but we cannot see it in terraform.
Debug Output
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
No