-
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
[Bug]: d/aws_lambda_function issue in aws provider 5.23.0 #34131
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
I get the same error when using │ Error: setting vpc_config: Invalid address to set: []string{"vpc_config", "0", "ipv6_allowed_for_dual_stack"}
|
Yes. Thanks. I made a mistake in my original report. I created the lambda as above, then get the error when I used it as a data resource
|
even after running the create lambda step with the provider 5.23 the error remains so my assumption is that the problem is in the data provider itself. |
Me, too. |
To make matters more confusing, I'm experiencing this error, but without any patterns related to whether it's a VPC Lambda or not. Some VPC Lambdas deploy without any issues, some of them get this error. |
same for me, we're using data to get a lambda function and we get the same error
code:
|
Same here with lambda with VPC config |
|
if you drop to |
Same for me, but in our case it shows the error when a lambda with a kafka trigger is created. |
Relates #34045. % make testacc TESTARGS='-run=TestAccLambdaFunctionDataSource_vpc$$' PKG=lambda
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/lambda/... -v -count 1 -parallel 20 -run=TestAccLambdaFunctionDataSource_vpc$ -timeout 360m
=== RUN TestAccLambdaFunctionDataSource_vpc
=== PAUSE TestAccLambdaFunctionDataSource_vpc
=== CONT TestAccLambdaFunctionDataSource_vpc
panic: Invalid address to set: []string{"vpc_config", "0", "ipv6_allowed_for_dual_stack"}
goroutine 1934 [running]:
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*ResourceData).Set(0xc0001f0880, {0xec203cf, 0xa}, {0xc5c7ea0, 0xc002115470})
/Users/ewbankkit/go/pkg/mod/github.com/hashicorp/terraform-plugin-sdk/[email protected]/helper/schema/resource_data.go:233 +0x291
github.com/hashicorp/terraform-provider-aws/internal/service/lambda.dataSourceFunctionRead({0xfffcee0, 0xc0018224e0}, 0xc0001f0880, {0xeba7520?, 0xc004692690})
/Users/ewbankkit/altsrc.1/github.com/terraform-providers/terraform-provider-aws/internal/service/lambda/function_data_source.go:321 +0x1cd2
github.com/hashicorp/terraform-provider-aws/internal/provider.interceptedHandler[...].func1(0x0?, {0xeba7520?, 0xc004692690?})
/Users/ewbankkit/altsrc.1/github.com/terraform-providers/terraform-provider-aws/internal/provider/intercept.go:111 +0x34b
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).read(0xfffcee0?, {0xfffcee0?, 0xc000ff6d20?}, 0xd?, {0xeba7520?, 0xc004692690?})
/Users/ewbankkit/go/pkg/mod/github.com/hashicorp/terraform-plugin-sdk/[email protected]/helper/schema/resource.go:790 +0x87
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).ReadDataApply(0xc004dc77a0, {0xfffcee0, 0xc000ff6d20}, 0xc0001f0480, {0xeba7520, 0xc004692690})
/Users/ewbankkit/go/pkg/mod/github.com/hashicorp/terraform-plugin-sdk/[email protected]/helper/schema/resource.go:1015 +0x150
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*GRPCProviderServer).ReadDataSource(0xc0067c5ef0, {0xfffcee0?, 0xc000be5e90?}, 0xc0052f2080)
/Users/ewbankkit/go/pkg/mod/github.com/hashicorp/terraform-plugin-sdk/[email protected]/helper/schema/grpc_provider.go:1237 +0x38f
github.com/hashicorp/terraform-plugin-mux/tf5muxserver.(*muxServer).ReadDataSource(0xfffce38?, {0xfffcee0?, 0xc000be5bc0?}, 0xc0052f2080)
/Users/ewbankkit/go/pkg/mod/github.com/hashicorp/[email protected]/tf5muxserver/mux_server_ReadDataSource.go:36 +0x1b5
github.com/hashicorp/terraform-plugin-go/tfprotov5/tf5server.(*server).ReadDataSource(0xc004bd83c0, {0xfffcee0?, 0xc000be5410?}, 0xc0001bc320)
/Users/ewbankkit/go/pkg/mod/github.com/hashicorp/[email protected]/tfprotov5/tf5server/server.go:699 +0x403
github.com/hashicorp/terraform-plugin-go/tfprotov5/internal/tfplugin5._Provider_ReadDataSource_Handler({0xe926400?, 0xc004bd83c0}, {0xfffcee0, 0xc000be5410}, 0xc0004fc070, 0x0)
/Users/ewbankkit/go/pkg/mod/github.com/hashicorp/[email protected]/tfprotov5/internal/tfplugin5/tfplugin5_grpc.pb.go:503 +0x170
google.golang.org/grpc.(*Server).processUnaryRPC(0xc0026903c0, {0x1000ab20, 0xc00656c340}, 0xc001ef4ea0, 0xc00654e4e0, 0x16642f68, 0x0)
/Users/ewbankkit/go/pkg/mod/google.golang.org/[email protected]/server.go:1376 +0xdd2
google.golang.org/grpc.(*Server).handleStream(0xc0026903c0, {0x1000ab20, 0xc00656c340}, 0xc001ef4ea0, 0x0)
/Users/ewbankkit/go/pkg/mod/google.golang.org/[email protected]/server.go:1753 +0xa36
google.golang.org/grpc.(*Server).serveStreams.func1.1()
/Users/ewbankkit/go/pkg/mod/google.golang.org/[email protected]/server.go:998 +0x98
created by google.golang.org/grpc.(*Server).serveStreams.func1
/Users/ewbankkit/go/pkg/mod/google.golang.org/[email protected]/server.go:996 +0x18c
FAIL github.com/hashicorp/terraform-provider-aws/internal/service/lambda 214.807s
FAIL
make: *** [testacc] Error 1 |
Me too!
|
This functionality has been released in v5.23.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! |
Documents deployed on release 2023.43.0: Migration K8S to ECS |
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.5.5
AWS Provider Version
5.23.0
Affected Resource(s)
Expected Behavior
Created lambda function. worked under 5.22.0
Actual Behavior
got error
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
Ran the terraform code using AWS provider 5.22.0. It runs fine.
Under AWS provider 5.23.0 I get the error.
Reverting back to 5.22.0 resolves the issue
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: