LambdaClient InvokeCommand response is missing StatusCode

[thekiwi]

Describe the bug

When executing the LambdaClient send() with an InvokeCommand, the response returned does not include the StatusCode field. The TypeScript definitions suggest it should (and SDK v2 did include it)

Your environment

SDK version number

@aws-sdk/[email protected]

Is the issue in the browser/Node.js/ReactNative?

Node.js

Details of the browser/Node.js/ReactNative version

v12.13.1

Steps to reproduce

Code snippet:

const { LambdaClient, InvokeCommand } = require('@aws-sdk/client-lambda');

const credentials = { accessKeyId: process.env.AKID, secretAccessKey: process.env.SAK };

async function run() {
	const lambda = new LambdaClient({ credentials, region: 'eu-west-1' })

	const params = {
		InvocationType: 'Event',
		FunctionName: 'my_function',
		Payload: JSON.stringify({ foo: 'bar' })
	};
	const command = new InvokeCommand(params);
	const result = await lambda.send(command);
	console.log(JSON.stringify(result, null, 2));
}

run().catch(console.error);

Observed behavior

Here is the output of the above code:

{
  "$metadata": {
    "httpStatusCode": 202,
    "requestId": "00000000-0000-0000-0000-000000000000",
    "attempts": 1,
    "totalRetryDelay": 0
  },
  "Payload": {}
}

You can see it has no StatusCode field at the root level.

Expected behavior

According to the TypeScript definition of InvocationResponse and the API documentation I expect the response payload to include a StatusCode field containing the same as $metadata.httpStatusCode.

Additional context

Tried with both the 'legacy' Lambda class and the newer LambdaClient class, both have the same result.

[razor-x]

Can confirm I just hit this and is still an issue with latest version of the sdk.

[ajredniwja]

Seems to be a deserialization issue

aws-sdk-js-v3/clients/client-lambda/protocols/Aws_restJson1.ts

Line 5410 in b9c1904

StatusCode: undefined,

,
its under investigation already, I will discuss with the team for a possible fix to be made soon.

[AllanZhengYP]

Hey @thekiwi @ajredniwja this turns out to be an issue with the SDK generator. I pushed a fix in the linked PRs. Thank you a lot for bringing this up!

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.