-
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
Can't update API Gateway v2 domain name mTLS truststore version: BadRequestException: Invalid input. Expected one domain name configuration #18312
Comments
I can reproduce with a slightly modified acceptance test case:
|
Sniffing the AWS Console network traffic I can see that the domain name configuration is sent when updating just the S3 object version:
|
This has been released in version 3.34.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 CLI and Terraform AWS Provider Version
Affected Resource(s)
aws_apigatewayv2_domain_name
Terraform Configuration Files
Here's the resource in question:
The difficult bit about setting up this recreation is that you will need to have an Amazon issued (e.g. DNS / email verified)
aws_acm_certificate.domain_cert
to configure mTLS. I can include some additional config if needed, let me know!Debug Output
Expected Behavior
The update to
truststore_version
succeeds.Actual Behavior
The update to
truststore_version
failsSteps to Reproduce
Updating / tainting the
aws_s3_bucket_object.truststore_pem
resource or manually changing thetruststore_version
value is enough to trigger the error.Important Factoids
No, standard AWS deployment and basic API Gateway configuration
References
The text was updated successfully, but these errors were encountered: