Hi, eventually I managed to successfully deploy my...

# http4k

[Nicola]

Hi, eventually I managed to successfully deploy my code, as an api gateway lambda, to localstack ... locally (of course)..
I have created a "function url config" then tried to invoke one of my endpoint.
I get this error in logs, perhaps has someone seen it already?

: Execution environment startup failed: {"errorMessage":"method is invalid","errorType":"java.lang.IllegalStateException","stackTrace":["org.http4k.serverless.ApiGatewayV1AwsHttpAdapter.toHttp4kRequest(ApiGatewayV1.kt:34)","org.http4k.serverless.ApiGatewayV1AwsHttpAdapter.invoke(ApiGatewayV1.kt:41)","org.http4k.serverless.ApiGatewayV1AwsHttpAdapter.invoke(ApiGatewayV1.kt:31)","org.http4k.serverless.ApiGatewayFnLoader.invoke$lambda$0(ApiGatewayFnLoader.kt:24)","org.http4k.serverless.AwsLambdaEventFunction.handleRequest(AwsLambdaEventFunction.kt:15)

[dave]

you're probably using the wrong wrapper: ApiGatewayV1AwsHttpAdapter <-- use v2 instead?

[Nicola]

going to try

[Nicola]

uhm with V2 function is not created .. need to understand the difference ...

[Nicola]

ah no

[dave]

so there are 2 different types of API "rest" and "http", and 2 different types of payload version in "http".

[Nicola]

it's get created

[Nicola]

it was just slow

[Nicola]

it works!!! thanks a lot!

[dave]

np. 🙂

[dave]

#ofCourseItWorks 😉

[Nicola]

😄
response doesnt get to my client but this is not a http4k problem, i see the response in the logs. have a nice day

[dave]

anything else, just yell! 🙂

[Nicola]

Now I have a local working configuration
But I still don't understand the V1 <-> V2 ApiGateway problem I had before.
Now I am using the V2 version:

@Suppress("unused")
class MyAwsLambdaExposedFunction : ApiGatewayV2LambdaFunction(printingAppWithEnv())

I've read that V1 is basically REST API. V2 is for Http and Websocket.
I was quite sure my function is in REST style, why V1 does not work?
It depends on some http4k configuration?

[dave]

you probably want the HTTP v2 payload style (which is setup in your configuration for your lambda). The REST style is the old style which was using the AWS configured OpenAPI stuff.

[dave]

From the http4k pulumi/serverless tutorial you can see the payload version set here: :

const lambdaIntegration = new aws.apigatewayv2.Integration("hello-http4k-api-lambda-integration", {
    apiId: api.id,
    integrationType: "AWS_PROXY",
    integrationUri: lambdaFunction.arn,
    payloadFormatVersion: "1.0"
});

[Nicola]

ah ok I see
I haven't used pulumi, I've just used aws cli to create the function .
I will look for a parameter like that in the aws cli reference, but basically I was just trying to understand ..
So do you recommend the V2 version?

[dave]

See: https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-lambda.html

[dave]

the old payload format is absolutely no good for web traffic because it doesn't support multiple headers with the same name

[dave]

so, for example, you can't have more than one Cookie...

[dave]

I think of the REST and v1 HTTP as deprecated

[Nicola]

Very interesting! thank you very much

[dave]

no problem - we learned the hard way so you don't have to! 😂

[dave]

(when you start to wonder why your app isn't working and it turns out that some headers go missing 🙈 )

[Nicola]

ah really? that's incredible

[dave]

well it is more like a "ah shit" moment- that's why they did v2! If you want to see incredible, you should see the Tencent serverless functions... is is a bad ripoff of the AWS API.,,

[Nicola]

never heard of ... I guess I am lucky 🙂

[dave]

lol - they're massive out East - bit like Alibaba cloud. We have had the pleasure of integrating http4k with a load of APIs which are... let's just say... questionable. 😂