Lambda Qualified Invoke ARN
Closed this issue · 5 comments
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
Currently the Lambda resource has qualified_arn and invoke_arn. But there is no Invoke ARN for the Qualified ARN. This means when passing it into API Gateway, it doesn't use the provisioned capacity you might have set.
You can work around this by doing: replace(aws_lambda_function.function.invoke_arn, aws_lambda_function.function.arn, aws_lambda_function.function.qualified_arn), but that is a really ugly hack.
New or Affected Resource(s)
NA
Potential Terraform Configuration
NA
References
NA
@fishcharlie @justinretzolk I can take a look at this if that's alright
@teddylear Good with me. I haven't really looked at this code base at all, so it'd be greatly appreciated!
@fishcharlie Created a PR to hopefully resolve issue. Please let me know if there are any questions or concerns.
This functionality has been released in v4.31.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. 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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.