Clojurians Log v2

👋 I'm doing lambdas now, and I know who the experts are. I hadn't realised portkey was so focused on doing deployments to aws itself. I'm off to look for an API I can use to load things into cloudformation/terraform :)

Also, I'm the author of pack above ^^. It's not particularly special beyond generating a zip with a lib directory. I'd love to have portkey integration for it, or at least the generation of a jar part.

yeah, have experienced some friction on getting back to portkey, maybe I need deadline 🙂

portkey has had a more “integrated” focus in lifting code to AWS Lambda from the repl, but I think one could call just the part that makes the zip, and allow deployment to happen in cloudformation/terraform, although the initially we ran towards a repl experience

We have a policy on ensuring all resources are managed, in order to reduce the impact of lost resources. So exporting the code is key.

That could be the start of an horror movie. Never ask for a deadline thrice.

@dominicm I might consider doing things the other way round - use portkey for repl-driven development, especially of code that works against AWS resources you can’t easily simulate locally, in a dev scratchpad environment. Once you have something that looks like what you want, you could reify that code deployment as a custom resource in Cloudformation that uses the same portkey deploy code to push your lambdas to production in a repeatable, source-controllable fashion

Test what you fly/fly what you test :)

I have almost no Terraform so I cannot opine thereon

Yeah, I was thinking that it would make for a good REPL-tool, especially if I can mark it as such easily. I'm glad you're able to confirm this idea. I was interested in the tree-shaking function for production, but I realise now I'm potentially attributing it features it does not have. Beyond size reduction, what features does tree-shaking provide?