announcements

Project/library announcements ONLY - use threaded replies for discussions. Do not cross post here from other channels. Consider #events or #news-and-articles for other announcements.
Karol W贸jcik 2021-04-21T15:00:54.492100Z

I'm thrilled to announce a new version of holy-lambda 0.1.21 which now supports #babashka runtime 馃檪 Special thanks to @viesti and @borkdude! You're awesome guys! You can now use one of the following runtimes: - java - babashka (here is a proof https://bdsa1uru44.execute-api.eu-central-1.amazonaws.com/Prod/) - native https://github.com/FieryCod/holy-lambda For now, babashka is shipped in zip which is quite lame and makes the artifact super big (50mb). I'm aware that's a lot, therefore I will provide a special AWS Layer for babashka in the future. Please tag this announcement with :babashka: icon if you would like me to do it :) If you would like to give babashka runtime a spin then use run the following:

lein new holy-lambda example
cd example

make USE_BB=true deploy-native # For babashka
make deploy-native # For native-runtime
make deploy # For java runtime
To remove stack just run:
make destroy-stack
PS: Template copies /usr/bin/bb to project path, for now, therefore you need babashka on /usr/bin/ If you have any question visit #holy-lambda channel 馃檪

馃憤 3
20
馃檱 1
鉂わ笍 2
馃帀 2
2021-04-22T16:18:21.006600Z

Cool beans! Is there anything preventing this from being used with the clojure CLI & deps.edn, or is lein required?

Karol W贸jcik 2021-04-22T16:28:55.006900Z

It's not required 馃槃

馃憤 1
Karol W贸jcik 2021-04-22T16:29:13.007100Z

@metasoarous https://github.com/FieryCod/holy-lambda/issues/31

Jakub Hol媒 2021-04-22T18:56:41.013700Z

I believe somebody already made a layer with bb, though might not fit your needs.

Karol W贸jcik 2021-04-22T19:55:50.017600Z

Hi @holyjak! Yep I鈥檓 aware. I will base the layer on some of @dainius.jocas work ;)

馃憤 1
2021-04-23T06:16:09.021300Z

Hi, nice work 馃憤 @karol.wojcik if anything is needed just ping me

Karol W贸jcik 2021-04-23T06:16:49.022100Z

@dainius.jocas 1.Would love to know whether you pay anything for hosting the layer? 2. May I please tag you in the repo for the parts that were inspired by your work?

2021-04-23T06:23:55.022600Z

1. The layer was uploaded using my personal AWS account but to have the layer uploaded I didn't have to pay. AFAIK, you pay just for the usage of lambdas that uses some layer, i.e. the regular AWS price. 2. Yes, that would be great. I'm curious to learn which parts of my little hack helped others @karol.wojcik

Karol W贸jcik 2021-04-23T06:24:53.022800Z

1. So each time somebody use my layer I pay for it?

2021-04-23T06:30:13.023Z

No. The lambda layer is like the library in clojars: you just upload it (free for you), and whoever use it in whatever way they do it, you have nothing to do with paying anything. Another way to think that a layer is just a zip in some public AWS S3 bucket, i.e. you pay nothing, and you aren't paid.

Karol W贸jcik 2021-04-23T06:37:24.023200Z

Ok got it. That was exactly the part I was missing. Thank you so much.

Karol W贸jcik 2021-04-21T15:05:46.493100Z

Also adding support for babashka was very straightforward. If anybody is interested in reading the details, then here is a commit: https://github.com/FieryCod/holy-lambda/commit/7716803810fbf919dcbc65828a37782a7c4175ac