Clojurians Log v2

pod-babashka-aws 0.0.4 released: bumped deps and a fix for forwarding a system property by @i.slack

@lukaszkorecki I added caching to the aws sso credential_process script. So ready for usage I think 🙂 It also works with the aws cli https://gist.github.com/jeroenvandijk/ace7432be94d083e63729ac313a0b78f

@jeroenvandijk really cool - if I understand correctly, most SDKs can pick up the credential_process option, including bb's aws pod?

@lukaszkorecki yes, from experience I know this to be true for the aws cli (so maybe also python skd’s) and the java sdk (used by Amazonica). aws-api doesn’t support it yet (https://github.com/cognitect-labs/aws-api/issues/73)

Awesome, that's super helpful

@jeroenvandijk when you're done developing this, maybe we could add it to the docs of the pod

or to an examples dir

Yeah I was thinking of how to distribute this in a convenient way. I have more scripts like this in mind, so was actually thinking of a seperate repo. Maybe even installable via homebrew or something so it is easy to find and install

Also it becomes complex pretty quickly, so tests would be nice too

well, maybe as a gitlib?

could be helpful when using it as a library. gitlib’s don’t support adding binaries to the PATH, right?

well, you can check anything into git, but maybe not the best thing to do. why?

what kind of binary?

just to make it a bit more convenient. Like how you install babashka through homebrew and not having to manage everything yourself (including updates)

a binary as in chmod +x script/my-babashka.clj

btw, I'll most likely write my own version of the SSO provider, as for example - when configuring SSO you have to have a valid config with profiles - @jeroenvandijk version assumes that some of that is configured in source

I’ll look into it later. For now, I spend way too much time on everything related to this pod 😅

but this was also the pod / native aws thing you have tried to come up with for a long time... right? so not time wasted...?

@lukaszkorecki My script only assumes you give it the right arguments in your credentials file (region, account-id, role and start url).

@borkdude sorry definitely didn’t mean wasted! Just that I need to focus a bit on other things and not sure when I’ll get to wrapping all these other things properly

@jeroenvandijk if you are distributing .clj files, I think gitlibs are the way to go.

(require '[babashka.deps :as deps])
(deps/add-deps '{:deps {jeroenvandijk/scripts {:git/url "<https://github>..." :sha "..."}}})
(require '[jeroenvandijk.scripts.aws-thing :as aws-thing])

Yeah looks good! Thank you

Btw, I automated bumping the aws-api deps using a bb script: https://github.com/babashka/pod-babashka-aws/blob/main/script/update-deps.clj

ah smart

And we have already 5 contributors now in such a short time. I think it's a success. Thanks for the time you put into the credential stuff especially, the gnarliest bit :)

I have to thank for you sure! 🙏 For putting that much time in this and not even being a real AWS user (yet, right?)

Right, but we're moving to the cloud now at work too, so I'll probably be one soon (either AWS, or Azure)

I’m also happy with the result. I have spent a lot of time in getting AWS tools to compile with Graalvm. This will not be the last one I think

Ah nice. Good to hear you can start with Clojure tools from the start (when using AWS)