Fork me on GitHub

if someone has some time to spare. the GraalVM devs are working towards finalizing GraalVM 20. I was asked to do some testing see issue: if someone wants to help, go ahead!

Jakub Holý (HolyJak)14:02:10

A crazy question, will it (ever) be possible to run under bb? (Or perhaps I need to wait until @jeroenvandijk is done porting it to cljs? :))


scroll a little bit back, @stijn also asked this. maybe he has ideas on it


maybe a sci based project (like babashka, bootleg, etc) can be made custom tailored around this library if it doesn't work with bb as is


@holyjak if you're using bb at a company, might be nice to mention it here:

👎 8

ok, could always try 😃


@holyjak I have ported the assume-role api request map generation call to cljs. I think it's the hardest part. It includes the signing of the authorization headers. There is lots more though to be complete, but I think it should be possible to slowly get there. Running it under Babashka would require a bit more work I guess, unless all the cryptographic classes are available

Jakub Holý (HolyJak)17:02:36

Well if it is cljs then we could just run it with Planck / Lumo, bb doesn't add anything there...


@jeroenvandijk what about forking bb and adding it as a built-in library?

Jakub Holý (HolyJak)17:02:15

How to add a built-in library?


@holyjak the same way all other built-in libraries are added to babashka


check babashka.main and look for cheshire.core for example

👍 4

then it could be bb-aws-api

👍 4

Yeah would work too I guess


@holyjak Do you need the convenience of the library or do you just need to do some AWS call in a specific context? What I have is not convenient yet. Probably easier to shell out to the Python cli client

Jakub Holý (HolyJak)17:02:47

I need to script some aws interactions and would prefer clj(s) over python / JS out of principle :)

👍 4

I'll share what I have soon