Skip to content

Pass boto3 session to the MemoryClient constructor#90

Closed
manikawnth wants to merge 1 commit intoaws:mainfrom
manikawnth:main
Closed

Pass boto3 session to the MemoryClient constructor#90
manikawnth wants to merge 1 commit intoaws:mainfrom
manikawnth:main

Conversation

@manikawnth
Copy link

Issue #, if available:
#44

Description of changes:
Currently MemoryClient doesn't have the capability to pass the boto3 session which makes it difficult to point to named profiles.

Change:
Allow MemoryClient to accept boto3.Session session as an optional parameter. Honor the existing region_name to prevent backward incompatibility.

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

jariy17 added a commit that referenced this pull request Mar 12, 2026
Allow MemoryClient to accept an optional boto3.Session, consistent with
MemorySessionManager. This enables named profiles, custom credentials,
and other session-level configuration.

Closes #44
Based on #90
@jariy17
Copy link
Contributor

jariy17 commented Mar 12, 2026

We merged a similar fix and it's now in v.1.4.6

@jariy17 jariy17 closed this Mar 12, 2026
@jariy17 jariy17 reopened this Mar 12, 2026
@jariy17 jariy17 requested a review from a team March 12, 2026 17:04
@jariy17
Copy link
Contributor

jariy17 commented Mar 12, 2026

We merged a similar fix and it's now in v.1.4.6

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.

2 participants