Bedrock ListFoundationModelsCommand error "byProvider"

[Depaa]

Describe the bug

ListFoundationModelsCommand should accept no parameters, instead it throws an error in the byProvider section.

Expected Behavior

With no parameter or with byProvider parameter, it should return the foundation models

Current Behavior

Returns error when passing no parameter, and returns 400 when passing the correct byProvider

to bypass you need to use one of the other filters like "byInferenceType"

Reproduction Steps

const {
  BedrockClient,
  ListFoundationModelsCommand,
} = require('@aws-sdk/client-bedrock');
const client = new BedrockClient({ region: process.env.REGION || 'us-east-1' });

const command = new ListFoundationModelsCommand();
const res = await client.send(command);

Possible Solution

No response

Additional Information/Context

No response

SDK version used

3.441.0

Environment details (OS name and version, etc.)

Windows

[RanVaknin]

Hi @Depaa ,

The syntax for v3 is to supply an empty object when no params are needed. So:

const {
  BedrockClient,
  ListFoundationModelsCommand,
} = require('@aws-sdk/client-bedrock');
const client = new BedrockClient({ region: process.env.REGION || 'us-east-1' });

- const command = new ListFoundationModelsCommand();
+ const command = new ListFoundationModelsCommand({});
const res = await client.send(command);

Thanks,
Ran~

[Depaa]

Hey @RanVaknin just to let you know the bug has been fixed in one of the latest versions of the SDK. Before the fix, if you happen to use 'byProvider' it would have returned status code 400 every time. I'm just glad it works now

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