-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
aws_cloudwatch_event_target panics if sqs_target block is empty #19945
Comments
I am drafting a PR that I think should resolve this. |
Relevant code: terraform-provider-aws/aws/resource_aws_cloudwatch_event_target.go Lines 670 to 680 in 7137144
|
This functionality has been released in v3.48.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 issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Terraform CLI and Terraform AWS Provider Version
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
https://gist.github.com/packrat386/b88da9175a551d4ab5968c8c87387887
Panic Output
Expected Behavior
This should not crash and add a cloudwatch event target to an SQS queue with no message_group_id.
Actual Behavior
It crashed
Steps to Reproduce
terraform apply
https://github.com/packrat386/tf_sqs_issue_repro
Important Factoids
N/A
I'm aware that this is a rather silly bug, as one should avoid adding the block if one does not have a message_group_id, but the provider still ought to handle it gracefully.
The text was updated successfully, but these errors were encountered: