[Refactor] Consolidate Bedrock OpenCode registration - #1315
Draft
roomote-roomote[bot] wants to merge 1 commit into
Draft
[Refactor] Consolidate Bedrock OpenCode registration#1315roomote-roomote[bot] wants to merge 1 commit into
roomote-roomote[bot] wants to merge 1 commit into
Conversation
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changed
Consolidated the common Bedrock OpenCode provider registration algorithm and replaced repeated three-provider call chains with one shared composition helper. Provider-specific transports and option merge order remain explicit, with focused coverage for all three registrations.
Why this change was made
PR #1293 centralized Bedrock provider setup but left model collection, provider cloning, option merging, and model-map assembly duplicated across registrations and runtime call sites. Keeping that algorithm in one place reduces the risk of Bedrock providers drifting as support evolves.
Impact
There is no intended user-facing behavior change. Bedrock Mantle Anthropic, Bedrock Mantle OpenAI, and native Amazon Bedrock retain their existing endpoints, SDK transports, region validation, model merging, and option precedence with less maintenance duplication.