What is the difference between the Linux and Linux static version of the artefacts?
The difference is the way it's compiled with GraalVM. https://www.graalvm.org/reference-manual/native-image/StaticImages/#:~:text=Static%20native%20images%20are%20statically,use%20in%20a%20Docker%20container.
@borkdude I have tried adding next.jdbc.result-set/as-arrays
but it increased compile time from 5 to 20 minutes. (Perhaps because it uses protocols?) These are quite useful but I guess not worth the increased compilation time (though it will be less on a better machine), thoughts?
Thanks for the digging. You can post an issue at https://github.com/babashka/babashka-sql-pods/ about this, as this function might also be useful for the sql pods and I'll take a look at it
In fact, I would like to receive a PR for the functions you want to add in babashka also over there, if you want, since it's easier to see if things blow up there, since there are actual CI builds with jdbc over there
Where can I quickly learn enough to understand how to port the change to the pods? As I know you, there is a document page just for that 🙂
@holyjak The pod documentation is here: https://github.com/babashka/pods The place where the functions are hooked up is here: https://github.com/babashka/babashka-sql-pods/blob/05c5d9512713d834c544e2d6c592d4988ed454de/src/pod/babashka/sql.clj#L99
I need to run aws cli command and work further with its output. What is the way to do it in modern bb? Just shell/sh
?
I think that's pretty common to do. You can also use babashka.process
if you need a longer running process
@holyjak There is also https://github.com/tzzh/pod-tzzh-aws which has lots of working features, but it currently doesn't let you upload a file to s3 (correct @thomas.ormezzano?)
Yes - haven’t add time to fix this but otherwise it supports a lot of features