Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation specifies defaults but they are not actually used #1113

Closed
Ten0 opened this issue Mar 25, 2024 · 2 comments
Closed

Documentation specifies defaults but they are not actually used #1113

Ten0 opened this issue Mar 25, 2024 · 2 comments
Labels
documentation This is a problem with documentation needs-triage This issue or PR still needs to be triaged.

Comments

@Ten0
Copy link
Contributor

Ten0 commented Mar 25, 2024

Describe the issue

Documentation explicitly specifies that the following fields have defaults:
image

But they are actually not applied. If the builder doesn't explicitly specify them, they will instead be explicitly be set to None
image

This makes the request fail with error:

ValidationException: The provided Content Type is invalid or not supported for this model

Setting those explicitly on InvokeModelFluentBuilder avoids the error:

builder
    .accept("application/json")
    .content_type("application/json")

Links

https://docs.rs/aws-sdk-bedrockruntime/1.18.0/aws_sdk_bedrockruntime/operation/invoke_model/builders/struct.InvokeModelFluentBuilder.html
https://docs.rs/aws-sdk-bedrockruntime/1.18.0/aws_sdk_bedrockruntime/operation/invoke_model/struct.InvokeModelInput.html

@Ten0 Ten0 added documentation This is a problem with documentation needs-triage This issue or PR still needs to be triaged. labels Mar 25, 2024
@Ten0 Ten0 changed the title (short issue description) Documentation specifies defaults but they are not actually used Mar 25, 2024
@Ten0
Copy link
Contributor Author

Ten0 commented Mar 25, 2024

closing in favor of #1114 (for more appropriate tag)

@Ten0 Ten0 closed this as completed Mar 25, 2024
Copy link

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation This is a problem with documentation needs-triage This issue or PR still needs to be triaged.
Projects
None yet
Development

No branches or pull requests

1 participant