@aws-sdk/client-codedeploy: SerializationException: Start of list found where not expected

[thoroc]

Checkboxes for prior research

• I've gone through Developer Guide and API reference
• I've checked AWS Forums and StackOverflow.
• I've searched for previous similar issues and didn't find any solution.

Describe the bug

package version: "@aws-sdk/client-codedeploy@*": "3.848.0"

I am trying to get the deployment for a specific deploymentId but I am getting SerializationException: Start of list found where not expected which implies that I am passing an Array somehow to the client, despite me passing a string.

Regression Issue

• Select this option if this issue appears to be a regression.

SDK version number

@aws-sdk/client-codedeploy@3.848.0e

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

deno 2.4.1 (stable, release, aarch64-apple-darwin) v8 13.7.152.6-rusty typescript 5.8.3

Reproduction Steps

Code to reproduce:

import {
  type DeploymentInfo,
  GetDeploymentCommand,
  type GetDeploymentCommandInput,
  type GetDeploymentCommandOutput,
} from "npm:@aws-sdk/client-codedeploy";

const deploymentId = 'd-FOOBAAA';
const input: GetDeploymentCommandInput = { deploymentId };

console.log("Running query with options:", JSON.stringify(input, null, 2));

const command = new GetDeploymentCommand(input);

console.log(
  "Executing command to get deployment details...",
  JSON.stringify(command, null, 2),
);

const response: GetDeploymentCommandOutput = await client.send(command);

The console logs are showing the following:

Running query with options: {
  "deploymentId": [
    "d-FOOBAAA"
  ]
}

and

{
  "middlewareStack": {},
  "input": {
    "deploymentId": [
      "d-FOOBAAA"
    ]
  }
}

Observed Behavior

error: Uncaught (in promise) SerializationException: Start of list found where not expected
    at throwDefaultError (file:///Users/<username>/Library/Caches/deno/npm/registry.npmjs.org/@smithy/smithy-client/4.4.8/dist-cjs/index.js:388:20)
    at file:///Users/<username>/Library/Caches/deno/npm/registry.npmjs.org/@smithy/smithy-client/4.4.8/dist-cjs/index.js:397:5
    at de_CommandError (file:///Users/<username>/Library/Caches/deno/npm/registry.npmjs.org/@aws-sdk/client-codedeploy/3.848.0/dist-cjs/index.js:3805:14)
    at Object.runMicrotasks (ext:core/01_core.js:692:26)
    at processTicksAndRejections (ext:deno_node/_next_tick.ts:59:10)
    at runNextTicks (ext:deno_node/_next_tick.ts:76:3)
    at eventLoopTick (ext:core/01_core.js:185:21)
    at async file:///Users/<username>/Library/Caches/deno/npm/registry.npmjs.org/@smithy/middleware-serde/4.0.8/dist-cjs/index.js:36:20
    at async file:///Users/<username>/Library/Caches/deno/npm/registry.npmjs.org/@smithy/core/3.7.0/dist-cjs/index.js:193:18
    at async file:///Users/<username>/Library/Caches/deno/npm/registry.npmjs.org/@smithy/middleware-retry/4.1.17/dist-cjs/index.js:320:38

Expected Behavior

Get the deployment details (object) returned.

Possible Solution

Maybe bypass the Command and create a Smithy one directly to pass to the client?

Additional Information/Context

This is a typescript project running on Deno. I appreciate that it might complicate a bit things since there isn't any option for alternative NodeJS runtime.

[aBurmeseDev]

Hi @thoroc - thanks for reaching out.

I ran the same code in Node and the console logs are showing deploymentId as string which is correct according to service model:

aws-sdk-js-v3/clients/client-codedeploy/src/models/models_0.ts

Line 5460 in 512c493

deploymentId: string | undefined;

---

Code

[github-actions]

This issue has not received a response in 1 week. If you still think there is a problem, please leave a comment to avoid the issue from automatically closing.

[thoroc]

@aBurmeseDev Ok this weird and seems to be tied to my local setup rather than the lib. Thank you for your time.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

[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.