00:07 <FromGitter> <Blacksmoke16> Main changes were: ⏎ ⏎ 1) No real need to have this in a module/method, can just do everything on the top level given its a simple scrip ⏎ 2) Use `JSON::Serializable`, more of a preference of mine, for this use case `JSON.parse` is totally fine ⏎ 3) Parse the JSON as its ouput by the process, no need to store it in memory ... [https://gitter.im/crystal-lang/crystal?at=6360632c880fe76caa1ed6e9]

00:08 <FromGitter> <Blacksmoke16> the one catch with building/deploy using that command is you need to ensure the target system has the runtime libs available. i.e. pcre, etc. Static builds can also be done if needed. each has their pro and cons

00:58 <FromGitter> <sergiotapia> Thanks a bunch will digest so far Crystal seems lovely

22:49 <FromGitter> <wwalker> Anyone here know about AWS? I'm trying to make an AWS request without passing any credentials (it will run on a machine with IAM roles that give it magical powers.) I'm using maiha/sqs.cr, which uses taylorfinnell/awscr-signer. Maybe someone here understands AWS (or the python boto code?) enough to tell me where to start to modify taylorfinnell/awscr-signer to allow no credentials.

22:52 <FromGitter> <Blacksmoke16> how do other langs handle it? i.e. is what you're doing even possible?

22:53 <FromGitter> <wwalker> Yes, I'm porting some horrendous python with boto to crystal. The python code runs fine without credentials. Just the "signer" lib in crystal doesn't expect you to pass no creds.

22:54 <FromGitter> <Blacksmoke16> ah 👍

22:57 <riza> @wwalker it's unfortunately not a trivial operation. you have to fetch credentials from an aws internal service ip address and then sign your request with those credentials

22:58 <FromGitter> <wwalker> riza: you mean an STS call?

23:01 <riza> you might be able to accomplish it with that

23:01 <riza> I'm not sure

23:02 <Ober> thanks riz

23:03 <riza> I've done it by hand a time or two but it's been _years_

23:05 <riza> i feel like it was a request to 169.254.169.254 something

23:05 <riza> https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html

23:05 <wwalker> curl 169.254.169.254/latest/meta-data/identity-credentials/ec2/security-credentials/ec2-instance

23:05 <wwalker> Thank you riza!

23:06 <riza> there it is

23:06 <riza> put that in a shard wouldja i'll probably need that someday :D

23:06 <Ober> we'll do a pr for the crystal

23:11 <Ober> the shard rather

23:50 <wwalker> riza: weird thing, if I take the data from that curl and put in (reformatted correctly) into .aws/credentials, or plug it into the crystal code (signer or sqs) it doesn't work :-( Back to the drawing board tomorrow...

23:59 <wwalker> riza: I had the wrong URL. That one has the right fields, but doesn't work. This one (changing the last path element based on your machine's iam profile) does work! curl 169.254.169.254/latest/meta-data/iam/security-credentials/gitlab_infrastructure_runner (if you curl without the last element, it will show your the last element's name)