Skip to content

feat(bedrock): stream redactedContent events #229

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

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

awsarron
Copy link
Member

Description

Added support for the redactedContent field in ReasoningContentBlock from AWS Bedrock API.

Based from #99 from @mazyu36.

Related Issues

#99

Documentation PR

N/A

Type of Change

  • New feature

Testing

  • hatch fmt
  • hatch run test-lint
  • hatch test

Checklist

  • I have read the CONTRIBUTING document
  • I have added tests that prove my fix is effective or my feature works
  • I have updated the documentation accordingly
  • I have added an appropriate example to the documentation to outline the feature
  • My changes generate no new warnings
  • Any dependent changes have been merged and published

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@awsarron awsarron enabled auto-merge (squash) June 16, 2025 12:22
@awsarron awsarron changed the title Feature/redacted content feat(bedrock): stream redactedContent events Jun 16, 2025
redacted_callbacks = [args for args in callback_args if "redactedContent" in args]
assert len(redacted_callbacks) == 2

assert redacted_callbacks[0]["redactedContent"] == b"encoded_data_1"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we do an assert redacted_callbacks[0] == {... entire object } to make this more readable?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants