refactor: GH-3620 Add BedrockChatOptions
to Bedrock
#3770
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a dedicated
BedrockChatOptions
class for the Bedrock module, replacing the previously used defaultToolCallingChatOptions
. This change aims to better accommodate Bedrock's unique features and parameter requirements, thereby enhancing the module's independence and maintainability.Additionally, this PR also fixes the issues mentioned in issue: #3620 .
This PR includes the following main changes:
Added the
BedrockChatOptions
class: This class is introduced to centrally manage chat configuration options when interacting with Bedrock models.Replaced the
options
implementation inBedrockConverseProxyChatProperties
: The previously used configuration class has been replaced with the newly introducedBedrockChatOptions
to ensure consistency and maintainability of the configuration.Updated the configuration usage in related model classes: All references to
ToolCallingChatOptions
have been replaced withBedrockChatOptions
to better align with the specific configuration requirements of Bedrock.Added targeted unit tests: Unit tests have been added for
BedrockChatOptions
and its related logic to ensure functional correctness and future maintainability.Fixes: #3620