Adding a status to response causing an error about functions HOT 6 CLOSED

weird! I'll investigate today --- thx for the heads up

from functions.

quick update: just reproduced this and looking into a fix!

from functions.

Update 2: that was fun. I have a fix! If you are feeling adventurous you could apply it manually.

You'll need to update the Integration Response body mapping template for application/json for the 403, 404 and 500 statuses.

#set($raw = $input.path('$.errorMessage'))
#set($len = $input.path('$.errorMessage').length() - 1)
#set($body = $raw.substring(25, $len))
$body

The long story short API Gateway utils.parseJson returns values that do not stringify back to JSON. So we have the above hack which substrings the JSON payload out. It is not pretty but it works. I'll try to land this back into arc-workflows as soon as I can. (Which then you could just delete the routes in API Gateway and regenerate with npm run create.

https://6nfxj2b5v4.execute-api.us-east-1.amazonaws.com/staging/api

from functions.

Ok got to it! Fixed in architect/[email protected]. If you delete the offending routes in API Gateway and then recreate them with npm run create they should work as expected. Let me know how you go and I'll keep the bug open 👍

from functions.

Nice one (sorry for slow reply) - upgraded to architect/[email protected] and working great 👍

from functions.

awesome!! thx for helping work thru it 💯

from functions.