I’ll do an update probably at the end of the week with some documentation

Took session token usage to master by cherry-picking from low-conform and did a rebase on master in low-conform. Should have made the change to master in the first place, the large diff that I was looking at was caused by whitespace changes only.

so as a warning, please do git pull --rebase in low-conform branch next time when you pull

ok, got it

https://github.com/portkey-cloud/aws-clj-sdk/blob/master/src/portkey/aws.clj#L95

nice !

wait a second I check

nope 😉

it’s okay

(case :a
    (:a :b) true) => true

ah true, just as the docstring says, just haven’t used the (test-constant1 ... test-constantN) result-expr form

So I think I will have time to make some s3 request thiis week as I am now able to make the request components

I was thinking about cleaning up a bit

indeed, I was focusing on the ser/resp part but gen-operation-xml/json/etc are way to complicated right now

And I think I have a way to simplify

my goal is to let you guys take some other stuff to work on and right now it’s to messy

mostly because I was way too focus

sorry about that ^^

@viesti I am not sure if I recall well but I think you once talked about a docker for testing

It would be awesome if we could test most of the sdk(s) for the sake of the project

there are projects for faking aws api’s

what’s your advice on testing apis ?

any idea what we could do ?

thinking that cleaning up (removing unused arguments) and refactoring in the hammock might be option (god hammock time blasphemy :))

lol

true

https://github.com/localstack/localstack

haven’t used but could be worth a look

it’s definitly a concern

a little change in gen files can have impact on all apis ^^

I guess I boobytrapped myself by adding x-amz-security-token

talking about tests…

anyway, tests with localstack fixture (such that one can run test body against a running localstack in the repl) might be neat

but sleep now