harris-chris
commented
6 months ago Hello - yes, I can relate to that situation myself. It isn't so much that this isn't supported in Jot.jl, more that it's not supported in AWS Lambda at all. There's a section in the documentation on this, but it just suggests what you're trying to avoid: https://harris-chris.github.io/Jot.jl/stable/Guide/#Working-around-the-one-function-per-container-limit
On Fri, Apr 12, 2024 at 9:38 AM Micah Rufsvold @.***> wrote:
I can't quite tell from the documentation if there's already structures for doing this.
Let's say I have a package that has 5 different functions that I want to turn into Lambda functions. I'm aware that I could have one top level function that switches based on an input parameter, But it's nice to have separate functions with separate identities. However, I prefer not to pay for compiling separate images and storing separate images for each of these functions when all I really need is one image with multiple entry points.
Is that supported in Jot.jl?
— Reply to this email directly, view it on GitHub https://github.com/harris-chris/Jot.jl/issues/46, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALDMVSFZOKSPI6ZP3ZBQ4I3Y44UHRAVCNFSM6AAAAABGDHG7KSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZTQOBSGQ4TGNA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
mrufsvold
I can't quite tell from the documentation if there's already structures for doing this.
Let's say I have a package that has 5 different functions that I want to turn into Lambda functions. I'm aware that I could have one top level function that switches based on an input parameter, But it's nice to have separate functions with separate identities. However, I prefer not to pay for compiling separate images and storing separate images for each of these functions when all I really need is one image with multiple entry points.
Is that supported in Jot.jl?