:thinking_face:

thinking about “http data->Clojure function arguments” transformation

we have one a bit hard-coded way now, ring does this by first having representation for http data and with idea of middleware which are function chains that transform the data and with compojure, which offers a set of macros to generate a handler and in the macro body one writes code that uses the data

elsewhere there is this idea of interceptors

anyway, I find the “lift function” idea still neat

hmm

@viesti don’t forget, the core is deploy! not mount!. mount! is only the first of its kind, so we may still have lift function as a usecase and expose a ring webapp as another

yes

(pk/ring!)

err 🙂

or pk/mount-doom! (since you throw a ring in)

More seriously

I feel that using swagger for setting up an AWS_PROXY is overkill

yeah, might be, the aws-java-sdk api looked daunting without swagger when we were supporting only query params

whats’s the actual http api like?

so wildcard on / path would swallow all requests

trying to figure details out, I believe it’s a PutIntegration with type “AWS_PROXY”

either pk/mount-doom! should either not take path and use /, or maybe user should define say /pets* or even direct /pets/{proxy+} (aws specific notation)

didn’t figure out details before, ended up trying things out in the console and exporting swagger and starting from there since the api gateway http-api (api :allthethings:) didn’t open up to me 🙂

yeah, prefixing support would be necessary

hum, should add CircleCI integration to this channel

so AWS protocols are not not homogeneous

rest-json is different for lambda and api-gw

I have to dispatch on the response content type

being able to publish ring handlers would be great… it makes it easier to grow an app from a simple live coded lambda to a larger app, like an uberjar with beanstalk…. without changing the code

https://circleci.com/gh/portkey-cloud/portkey/21

yes

can we have a CircleCI integration that shames the author of the breakage publicly?

> This app is restricted for this workspace. Browse approved apps

would need to ask admins of this slack

would think that we’r not only ones that would find this useful

well this slack is running low on integrations for the free tier

Let’s just write a lambda bot...

haa! 🙂

Raaaahhh HAL, okay it’s hypermedia I should like it but it wouldn’t be able to open the pod bay doors even if it wanted...

jokes apart, my peeves against HAL are that: • you can’t know when a link is safe to follow • requests shapes are described out of band in an unspecified fashion

http://stateless.co/hal_specification.html

oh and HAL is one of these systems where one value is the same as a singleton collection containing this value

simple way

> In short, it will make your API easier to work with and therefore more attractive to client developers.

you should feel attracted

don’t get me started on the sorry state of hypermedia for apis

short version: it’s because it makes little business sense

so had much less thorough look on HAL and thought that if the thing eats swagger (which I needed to learn as well), I'm much more happy :)

??

to say that I was happy with swagger import/put by the java sdk for api creation and update, didn't read enough about HAL

HAL is abstracted behind the SDK but when generating a SDK you have to face it.

one thing I wanted to ask is whether some kind of layer on top of the sdk is going to be part of this project, so for instance a layer that converts clojure data to the input to a DynamoDB putItem