serverstatus and serverstartstop API Gateway Lambda fails

[rjaduthie]

There seems to be some slight misconfiguration for the updownstatus API. The API responds with 500 and the Lambda logs show that the handler is not found:

{
    "errorType": "Runtime.HandlerNotFound",
    "errorMessage": "index.handler is undefined or not exported",
    "stack": [
        "Runtime.HandlerNotFound: index.handler is undefined or not exported",
        "    at UserFunction.js.module.exports.load (file:///var/runtime/index.mjs:1038:15)",
        "    at async start (file:///var/runtime/index.mjs:1200:23)",
        "    at async file:///var/runtime/index.mjs:1206:1"
    ]
}

Both endpoints are affected.

I'll take a look at this, but it'll be the earliest tomorrow.

[rileydakota]

Wondering if it doesn't like this recent change for some reason:

valheim-ecs-fargate-cdk/resources/serverstatus.ts

Line 38 in 61bf2bb

const handler: APIGatewayProxyHandler = async (event: APIGatewayEvent, context: Context) => {

Although it appears to still be exported here:

valheim-ecs-fargate-cdk/resources/serverstatus.ts

Line 53 in 61bf2bb

export default handler;

The original:

valheim-ecs-fargate-cdk/resources/serverstatus.ts

Line 29 in 72bee85

exports.handler = async (event, context, callback) => {

I should have some time to take a look tonight as well

[rjaduthie]

My initial tests, it looks like reverting this fixes the issue. I've still got some work to figure out how to use this API properly; it's late here, so maybe I can finish testing another day.

[rjaduthie]

OK, didn't leave this. The fix is substitute the const handler [...] lines with:

exports.handler = async (event: APIGatewayEvent, context: Context) => { 

However, the startstop endpoint doesn't seem to actually change the desire count of the Fargate task. I should probably create a new issue for this though.

[rjaduthie]

Minimal change fix in PR #33