-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
[Bug]: AWS Batch 'panic: interface conversion: interface {} is nil, not map[string]interface {}' #38710
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Update: Adding EITHER a retry strategy OR a timeout with the following code solved it. attempt_duration_seconds = 60 retry_strategy = {
attempts = 3
evaluate_on_exit = {
retry_error = {
action = "RETRY"
on_exit_code = 1
}
exit_success = {
action = "EXIT"
on_exit_code = 0
}
}
} I'm no Golang expert but I think the problem is doing type coercion on a |
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! |
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. |
Terraform Core Version
1.9.3
AWS Provider Version
5.61.0
Affected Resource(s)
aws_batch_job_definition
Expected Behavior
I am using the AWS Batch TF module: https://registry.terraform.io/modules/terraform-aws-modules/batch/aws/latest
But I believe the problem is with the underlying
aws_batch_job_definition
resource.I expect to be able to create the resources with the batch module.
Actual Behavior
Creating the resources initially with
terraform apply
works just fine. But even if the code remains completely unchanged, when runningterraform apply
again, the provider crashes.It looks like it's coming from the
/internal/service/batch.needsJobDefUpdate
function.Not the same issue, but looks similar: #22660, #17284
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: