Skip to content

Propogate tenantId header in notification plugin client calls#2121

Open
eirsep wants to merge 1 commit intoopensearch-project:mainfrom
eirsep:feat/tenant-context-notifications
Open

Propogate tenantId header in notification plugin client calls#2121
eirsep wants to merge 1 commit intoopensearch-project:mainfrom
eirsep:feat/tenant-context-notifications

Conversation

@eirsep
Copy link
Copy Markdown
Member

@eirsep eirsep commented May 5, 2026

No description provided.

@eirsep eirsep marked this pull request as ready for review May 6, 2026 00:56
@eirsep eirsep force-pushed the feat/tenant-context-notifications branch 4 times, most recently from bd87d18 to 9916161 Compare May 6, 2026 01:40
@nishtham-amazon
Copy link
Copy Markdown
Collaborator

Please see why some of the build workflows are failing.

@eirsep eirsep force-pushed the feat/tenant-context-notifications branch 2 times, most recently from 09dd3ab to e326dd4 Compare May 6, 2026 12:06
In MonitorRunner.runAction(), read currentTenantId() from the coroutine
context and re-inject it as a ThreadContext header after stashing. This
ensures the tenant ID is available when NotificationsPluginInterface
sends notifications via SecureClientWrapper.

Signed-off-by: Surya Sashank Nistala <snistala@amazon.com>
@eirsep eirsep force-pushed the feat/tenant-context-notifications branch from e326dd4 to a760359 Compare May 6, 2026 18:21
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.

3 participants