[feature] memory tool: use existing boto3 session #138
+589
−296
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.
Description
This PR enhances the memory tool with comprehensive boto3 session injection capabilities, enabling flexible AWS authentication patterns for accessing Amazon Bedrock Knowledge Bases. The changes add two new public functions (set_memory_session and get_memory_session) and extend the existing memory tool to support custom session management.
Key Changes:
New Capabilities:
[No specific issues referenced - this is a feature enhancement]
Documentation and sdk-python PR
Type of Change
[ ] Bug fix
[ ] New Tool
[x] Breaking change (extends existing tool with new parameters - backward compatible)
[ ] Other (please describe):
Testing
Manual Testing Completed:
Code Quality Checks:
Validation Scripts:
Checklist
[x] I have read the CONTRIBUTING document
[x] I have added tests that prove my fix is effective or my feature works
[x] I have updated the documentation accordingly
[x] I have added an appropriate example to the documentation to outline the feature
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published
Additional Quality Assurance:
[x] All 27 code examples in documentation are syntactically correct
[x] Function signatures match between implementation and documentation
[x] Session management follows AWS best practices
[x] Error handling provides clear user feedback
[x] Backward compatibility maintained for existing user