docs(proposals): How? for AWS Bedrock translation (#778) - #783
Open
mkoushni wants to merge 1 commit into
Open
Conversation
…y#778) Adds the implementation design for the AWS Bedrock (Converse + InvokeModel) sub-task split out of praxis-proxy#762, building on the accepted What?/Why? in 00762_api-translation.md. Signed-off-by: mkoushni <mkoushni@redhat.com>
mkoushni
force-pushed
the
proposal/778-bedrock-translation-how
branch
from
August 19, 2026 14:25
8456e71 to
2411789
Compare
This was referenced Aug 19, 2026
mkoushni
marked this pull request as ready for review
August 19, 2026 14:38
|
Proposal validation failed:
|
2 tasks
Contributor
|
LGTM |
alexsnaps
reviewed
Aug 19, 2026
alexsnaps
left a comment
alexsnaps
left a comment
Member
There was a problem hiding this comment.
I can't seem to find docs/proposals/00762_api-translation.md ?
What am I missing?
Generally tho, I think it's safe to move forward with the implementation of this already
| - "InvokeModel model-family scope (Anthropic-shaped body reuse vs. new adapters) reviewed by stakeholders" | ||
| - "Bedrock API key rotation/hot-reload strategy for credential_inject reviewed by stakeholders" | ||
| stakeholders: | ||
| - # TODO: add relevant maintainer/domain-expert handles before merge |
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
3 participants
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.
Summary
Adds the How? section for #778, one of the four per-provider sub-tasks split out of #762. Builds on the accepted What?/Why? in
docs/proposals/00762_api-translation.md.bedrock_translate,bedrock_stream_events) mirroring the existinganthropic_to_openai/anthropic_stream_eventsstructure.buffered_request_body) mechanism — no second routing hop needed.aws-smithy-eventstreamfor binary event-stream framing,apis/src/anthropic/to_openai/*for the InvokeModel Anthropic-family body, and the existingcredential_injectbearer-token seam for upstream auth (no SigV4 signing needed, per Bedrock API keys).Test plan