portkey

Portkey: from REPL to Serverless in one call
baptiste-from-paris 2018-09-16T13:44:43.000100Z

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

2018-09-16T17:00:40.000100Z

2018-09-16T17:01:10.000100Z

viesti 2018-09-16T17:02:22.000100Z

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.

viesti 2018-09-16T17:03:03.000100Z

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

baptiste-from-paris 2018-09-16T17:03:11.000100Z

ok, got it

2018-09-16T18:55:33.000100Z

baptiste-from-paris 2018-09-16T18:55:56.000100Z

nice !

baptiste-from-paris 2018-09-16T18:57:26.000100Z

wait a second I check

baptiste-from-paris 2018-09-16T18:57:58.000100Z

nope 😉

baptiste-from-paris 2018-09-16T18:58:03.000100Z

it’s okay

baptiste-from-paris 2018-09-16T18:58:25.000100Z

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

viesti 2018-09-16T19:08:35.000100Z

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

baptiste-from-paris 2018-09-16T19:09:51.000100Z

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

baptiste-from-paris 2018-09-16T19:10:27.000100Z

I was thinking about cleaning up a bit

baptiste-from-paris 2018-09-16T19:11:03.000100Z

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

baptiste-from-paris 2018-09-16T19:11:17.000100Z

And I think I have a way to simplify

baptiste-from-paris 2018-09-16T19:11:46.000100Z

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

baptiste-from-paris 2018-09-16T19:12:00.000100Z

mostly because I was way too focus

baptiste-from-paris 2018-09-16T19:12:06.000100Z

sorry about that ^^

baptiste-from-paris 2018-09-16T19:13:06.000100Z

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

baptiste-from-paris 2018-09-16T19:13:40.000100Z

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

viesti 2018-09-16T19:15:25.000100Z

there are projects for faking aws api’s

baptiste-from-paris 2018-09-16T19:15:58.000100Z

what’s your advice on testing apis ?

baptiste-from-paris 2018-09-16T19:16:09.000100Z

any idea what we could do ?

viesti 2018-09-16T19:16:41.000100Z

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

baptiste-from-paris 2018-09-16T19:16:56.000100Z

lol

baptiste-from-paris 2018-09-16T19:17:00.000100Z

true

viesti 2018-09-16T19:17:10.000100Z

https://github.com/localstack/localstack

viesti 2018-09-16T19:18:24.000100Z

haven’t used but could be worth a look

baptiste-from-paris 2018-09-16T19:18:58.000100Z

it’s definitly a concern

baptiste-from-paris 2018-09-16T19:19:17.000100Z

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

viesti 2018-09-16T19:23:39.000100Z

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

viesti 2018-09-16T19:23:46.000100Z

talking about tests…

2018-09-16T19:43:18.000100Z

viesti 2018-09-16T19:45:14.000200Z

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

viesti 2018-09-16T19:45:17.000100Z

but sleep now