Deployed API Gateway points to $LATEST

[texonidas]

As the title says. Rather than pointing to the most recently deployed version of the code, API Gateway is pointing to the unqualified ARN of the lambda function, which points to $LATEST.

The reason this is an issue is that you cannot use provisioned concurrency on $LATEST, even when aliased, which is causing some serious pain for me (massive cold start times, which is a separate issue in itself, but provisioning concurrency would fix).

Expected Behavior

API Gateway should point to f'{FunctionArn}:{Version}', so that provisioned concurrency can occur.

Actual Behavior

API Gateway points to FunctionARN.

Possible Fix

Kind of covered? I see there is already an open issue regarding provisioned concurrency, and this would be step to that working.

Steps to Reproduce

1. Deploy a project with Zappa, then view the ARN of the Lambda instance it points to.

Your Environment

• Zappa version used: 0.58.0
• Operating System and Python version: Lambda - Python 3.9

[github-actions]

Hi there! Unfortunately, this Issue has not seen any activity for at least 90 days. If the Issue is still relevant to the latest version of Zappa, please comment within the next 10 days if you wish to keep it open. Otherwise, it will be automatically closed.

[github-actions]

Hi there! Unfortunately, this Issue was automatically closed as it had not seen any activity in at least 100 days. If the Issue is still relevant to the latest version of Zappa, please open a new Issue.