Clojurians Log v2

Thinking that a Lambda will usually talk to some number of AWS services, so aws-api (or aws-java-sdk, haven't tested how well that compiles with native-image) probably get's used. Nice that there's a aws-api example (https://github.com/FieryCod/holy-lambda/tree/master/examples/sqs-example), thinking that should probably have pod-babashka-aws example too 🙂 https://github.com/babashka/pod-babashka-aws

since a pod is a subprocess to run, I guess pod-babashka-aws should then be either included as a dependency in a client project, or even bundled into the babashka layer, though then there are two things to updated in a layer: babashka and aws pod

hum, did layers have versioning... just thinking that if a user has many Lambdas that all share a layer and maybe just one of the Lambdas needs an update to the shared layer, then user has to take care that the updated layer works in all the other Lambdas too, hum

Holy-lambda will provide only one layer which will be versioned. Each time babashka bumps it's version or there is new Clojure version I will update a layer and user will have to manually (at least for now) update template.yml layer ARN. In next release holy-lambda will provide a special step to bundle pods (if user uses any) in native-deps/*. Therefore, you will be able to add arbitrary artifacts to deployment.zip.

ah right, version is in the layer ARN even

Ahh. Would love to implement babashka tasks

Still need to figure it out whether packed pods will work if passsed to a babashka classpath. Hope it will work that way

yeah, haven't used pods myself either, but would probably be neat to have holy-lambda example with this 🙂 https://github.com/babashka/pod-babashka-aws

Figuring that part out with borkdude.

thinking along the lines of

#?(
:bb
(require '[babashka.pods :as pods])
(pods/load-pod 'org.babashka/aws "0.0.5")
(require '[pod.babashka.aws :as aws])
:clj
(require '[cognitect.aws.client.api :as aws]))

(def s3 (aws/client {:api :s3}))

+ some magic to make the pod appear on bb, otherwise use clj branch elsewhere 😄

Yep. But you still have to provide pod to aws lambda runtime somehow

I would rather avoid re-downloading pod in runtime context 😄

Ok borkdude explained to me how it should work 😄

@anbz has joined the channel

@stask has joined the channel