Fork me on GitHub
#announcements
<
2021-04-21
>
Karol Wójcik15:04:54

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 🙂

babashka 55
🙇 3
👍 8
🎉 5
❤️ 4
Karol Wójcik15:04:46

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

metasoarous16:04:21

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

Karol Wójcik16:04:55

It's not required 😄

👍 2
Jakub Holý18:04:41

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

Karol Wójcik19:04:50

Hi @U0522TWDA! Yep I’m aware. I will base the layer on some of @U0FT43GKV work ;)

👍 3
Dainius Jocas06:04:09

Hi, nice work 👍 @UJ1339K2B if anything is needed just ping me

Karol Wójcik06:04:49

@U0FT43GKV 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?

Dainius Jocas06:04:55

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 @UJ1339K2B

Karol Wójcik06:04:53

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

Dainius Jocas06:04:13

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ójcik06:04:24

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