Any fresh insight into how to make provisioned concurrency work for Jets controllers?
I had some trouble with JetsPreheatJob permissions after the 4.x update and decided to take a crack at selectively implementing provisioned concurrency for a few of my controller functions that need to be always hot. The problem I’m running into is that AWS Lambda only lets you set provisioned concurrency for an alias or version of a function, but it can’t be an alias or version pointed to the $LATEST version.
Setting up a version was easy enough to test, but Jets still wants to call the $LATEST version of the function, so it’s not hitting my provisioned Lambdas at all.
Is there a way to tell Jets to call a specific function alias or version?
Is there a way to make jets use this AutoPublishVersion feature to automatically create a live alias pointing to a recent version of the deployed function?
Even if I can just hardcode the function version for now, it would be better than skipping my provisioned Lambdas entirely.
Really a question for @tung but if others have run into it I’m interested. I would be willing to take a crack at it a PR if you can give me some pointers on where this might go.