-
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
Crash with bad service_type in aws_vpc_endpoint_service #17419
Comments
Fuller stack trace:
terraform-provider-aws/aws/data_source_aws_vpc_endpoint_service.go Lines 137 to 159 in 798ac2f
<?xml version="1.0" encoding="UTF-8"?>
<DescribeVpcEndpointServicesResponse xmlns="http://ec2.amazonaws.com/doc/2016-11-15/">
<requestId>c2678f56-fe75-4374-b47e-870c376a4754</requestId>
<serviceDetailSet>
<item>
<acceptanceRequired>false</acceptanceRequired>
<availabilityZoneSet>
<item>us-west-2a</item>
<item>us-west-2b</item>
<item>us-west-2c</item>
<item>us-west-2d</item>
</availabilityZoneSet>
<baseEndpointDnsNameSet>
<item>s3.us-west-2.vpce.amazonaws.com</item>
</baseEndpointDnsNameSet>
<managesVpcEndpoints>false</managesVpcEndpoints>
<owner>amazon</owner>
<serviceId>vpce-svc-0b5d83f29260cde0d</serviceId>
<serviceName>com.amazonaws.us-west-2.s3</serviceName>
<serviceType>
<item>
<serviceType>Interface</serviceType>
</item>
</serviceType>
<tagSet/>
<vpcEndpointPolicySupported>true</vpcEndpointPolicySupported>
</item>
<item>
<acceptanceRequired>false</acceptanceRequired>
<availabilityZoneSet>
<item>us-west-2-lax-1a</item>
<item>us-west-2-lax-1b</item>
<item>us-west-2-wl1-den-wlz-1</item>
<item>us-west-2-wl1-las-wlz-1</item>
<item>us-west-2-wl1-sea-wlz-1</item>
<item>us-west-2-wl1-sfo-wlz-1</item>
<item>us-west-2a</item>
<item>us-west-2b</item>
<item>us-west-2c</item>
<item>us-west-2d</item>
</availabilityZoneSet>
<baseEndpointDnsNameSet>
<item>s3.us-west-2.amazonaws.com</item>
</baseEndpointDnsNameSet>
<owner>amazon</owner>
<serviceId>vpce-svc-0001be97e1865c74e</serviceId>
<serviceName>com.amazonaws.us-west-2.s3</serviceName>
<serviceType>
<item>
<serviceType>Gateway</serviceType>
</item>
</serviceType>
<tagSet/>
<vpcEndpointPolicySupported>true</vpcEndpointPolicySupported>
</item>
</serviceDetailSet>
<serviceNameSet>
<item>com.amazonaws.us-west-2.s3</item>
<item>com.amazonaws.us-west-2.s3</item>
</serviceNameSet>
</DescribeVpcEndpointServicesResponse> |
… update CHANGELOG for #17641 Reference: #17419 Output from acceptance testing in AWS Commercial: ``` --- PASS: TestAccDataSourceAwsVpcEndpointService_interface (21.03s) --- PASS: TestAccDataSourceAwsVpcEndpointService_ServiceType_Interface (22.39s) --- PASS: TestAccDataSourceAwsVpcEndpointService_ServiceType_Gateway (22.48s) --- PASS: TestAccDataSourceAwsVpcEndpointService_gateway (23.76s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom_filter (230.43s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom_filter_tags (235.33s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom (238.79s) ``` Output from acceptance testing in AWS GovCloud (US): ``` --- PASS: TestAccDataSourceAwsVpcEndpointService_interface (30.12s) --- PASS: TestAccDataSourceAwsVpcEndpointService_ServiceType_Interface (30.15s) --- PASS: TestAccDataSourceAwsVpcEndpointService_gateway (30.16s) --- PASS: TestAccDataSourceAwsVpcEndpointService_ServiceType_Gateway (30.16s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom_filter_tags (249.96s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom (259.01s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom_filter (261.24s) ```
…rom client-side to API (#17641) * data-soruce/aws_vpc_endpoint_service: Switch service_type filtering from client-side to API Reference: #17417 Output from acceptance testing in AWS Commercial: ``` --- PASS: TestAccDataSourceAwsVpcEndpointService_interface (12.25s) --- PASS: TestAccDataSourceAwsVpcEndpointService_ServiceType_Interface (12.65s) --- PASS: TestAccDataSourceAwsVpcEndpointService_ServiceType_Gateway (12.65s) --- PASS: TestAccDataSourceAwsVpcEndpointService_gateway (12.65s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom (217.41s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom_filter (219.87s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom_filter_tags (228.91s) ``` Output from acceptance testing in AWS GovCloud (US): ``` --- PASS: TestAccDataSourceAwsVpcEndpointService_gateway (16.05s) --- PASS: TestAccDataSourceAwsVpcEndpointService_interface (16.25s) --- PASS: TestAccDataSourceAwsVpcEndpointService_ServiceType_Interface (16.26s) --- PASS: TestAccDataSourceAwsVpcEndpointService_ServiceType_Gateway (16.26s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom_filter_tags (229.07s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom (229.30s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom_filter (229.52s) ``` * Update CHANGELOG for #17641 * data-source/aws_vpc_endpoint_service: Validate service_type argument, update CHANGELOG for #17641 Reference: #17419 Output from acceptance testing in AWS Commercial: ``` --- PASS: TestAccDataSourceAwsVpcEndpointService_interface (21.03s) --- PASS: TestAccDataSourceAwsVpcEndpointService_ServiceType_Interface (22.39s) --- PASS: TestAccDataSourceAwsVpcEndpointService_ServiceType_Gateway (22.48s) --- PASS: TestAccDataSourceAwsVpcEndpointService_gateway (23.76s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom_filter (230.43s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom_filter_tags (235.33s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom (238.79s) ``` Output from acceptance testing in AWS GovCloud (US): ``` --- PASS: TestAccDataSourceAwsVpcEndpointService_interface (30.12s) --- PASS: TestAccDataSourceAwsVpcEndpointService_ServiceType_Interface (30.15s) --- PASS: TestAccDataSourceAwsVpcEndpointService_gateway (30.16s) --- PASS: TestAccDataSourceAwsVpcEndpointService_ServiceType_Gateway (30.16s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom_filter_tags (249.96s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom (259.01s) --- PASS: TestAccDataSourceAwsVpcEndpointService_custom_filter (261.24s) ```
This has been released in version 3.33.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 for triage. Thanks! |
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. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Skipping. Trivial to reproduce.
Panic Output
Relevant lines:
Expected Behavior
A non-crash error indicating that no vpc endpoints were found. Possibly an error that
service_type
is invalid. Per the documentation,Gateway
andInterface
are valid values. The crash results from an invalid value.Actual Behavior
Crash
Steps to Reproduce
terraform init
terraform plan
The text was updated successfully, but these errors were encountered: