-
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
Api gateway authorizer authorizer_result_ttl_in_seconds
is not set to 0 on first run
#12633
Comments
I've done some testing with the aws cli this morning and i can recreate this issue in the aws console by not setting the /cc @DrFaust92 |
Fix has been merged and will release with upcoming |
This has been released in version 3.0.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)
aws_api_gateway_authorizer.api_authorizer
Terraform Configuration Files
There is a repo here with the full source:
https:/kevinkuszyk/terraform-aws-apigateway-authorizer-cache
Expected Behavior
I was expecting the authorizer to be created with the
authorizer_result_ttl_in_seconds
set to zero.Actual Behavior
It doesn't seem to be set. It shows like this in the aws console:
And a
terraform plan
after applying the config gives this (300
is the default value):Running
terraform apply
again will make the change, so it appears to be an issue with creating new resources.Steps to Reproduce
terraform apply
terraform plan
References
Other notes
I would attempt a fix, but I can't see anything wrong in the code. If someone can provide some guidance I will do what I can.
The text was updated successfully, but these errors were encountered: