list-custom-model does not filter by base or foundation model

[collimilo]

Describe the bug

Passing the --foundation-model-arn-equals or --base-model-arn-equals filters do not restrict the output of list-custom-model as stated by the documentation. It seems the filters are ignored. I see the same behavior in a Java application with the Java AWS sdk.

Expected Behavior

The --foundation-model-arn-equals or --base-model-arn-equals filters should behave as documented.

Current Behavior

The --foundation-model-arn-equals or --base-model-arn-equals filters do not restrict the output of list-custom-model to custom models with the matching base/foundation model. No error is reported.

Reproduction Steps

Assuming the output of aws bedrock list-custom-models is not empty:

• issue a aws bedrock list-custom-models --foundation-model-arn-equals or aws bedrock list-custom-models --base-model-arn-equals` request
• observe that the filters do not restrict the result

Possible Solution

No response

Additional Information/Context

No response

CLI version used

aws-cli/2.17.53 Python/3.11.10 Darwin/23.6.0 source/x86_64

Environment details (OS name and version, etc.)

osx 14.6.1

[adev-code]

Hello @collimilo, thanks for reaching out and finding the issue. I was able to reproduce the issue. I have reached out to the Bedrock service team. I'll let you know when I have any updates. In the meantime, if you have any follow-up questions, please do let me know. Thanks.

Ticket # for internal reference : P156988546

[collimilo]

Hello @collimilo, thanks for reaching out and finding the issue. I was able to reproduce the issue. I have reached out to the Bedrock service team. I'll let you know when I have any updates. In the meantime, if you have any follow-up questions, please do let me know. Thanks.

Ticket # for internal reference : P156988546

Thanks @adev-code ! No other questions for the moment

[github-actions[bot]]

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.