-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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_lambda_function resource causing plugin not to respond. #31583
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
I'm seeing the same issue and similar stack trace when Applying changes to IAM roles/policies using v5 provider (not Lambda) |
I can also reproduce this error with a simpler test case, unrelated to Lambda: provider "aws" {
region = "us-east-1"
}
variable "foobar" {
default = null
}
resource "aws_sqs_queue" "queue" {
tags = {
Foobar = var.foobar
}
} and the resulting error from
(edit) We use |
This functionality has been released in v5.0.1 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.2.3
AWS Provider Version
5.0.0_x5
Affected Resource(s)
aws_lambda_function
Expected Behavior
Should provision the lambda function resource.
Actual Behavior
Error: Plugin did not respond
│ The plugin encountered an error, and failed to respond to the
│ plugin.(*GRPCProvider).ApplyResourceChange call. The plugin logs may
│ contain more details.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
vars.tf
Steps to Reproduce
terraform apply. Seems to be happening on updates to the lambda.
Debug Output
No response
Panic Output
No response
Important Factoids
This worked with the previous 4.x provider. Seems to be happening when tags are not changing. When tags are changing during the run, we don't get the panic.
References
No response
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered: