Skip to content

Expose Nexus Endpoint in a Nexus Operation Handler#1437

Merged
Quinn-With-Two-Ns merged 3 commits intotemporalio:mainfrom
Quinn-With-Two-Ns:issue-1436
Apr 14, 2026
Merged

Expose Nexus Endpoint in a Nexus Operation Handler#1437
Quinn-With-Two-Ns merged 3 commits intotemporalio:mainfrom
Quinn-With-Two-Ns:issue-1436

Conversation

@Quinn-With-Two-Ns
Copy link
Copy Markdown
Contributor

@Quinn-With-Two-Ns Quinn-With-Two-Ns commented Apr 13, 2026

What was changed

Expose the Nexus Endpoint to the SDK.

Why?

So the handler knows what endpoint the request originally came from for visibility and per endpoint encryption

Checklist

  1. Closes

  2. How was this tested:

  1. Any docs updates needed?

closes #1436


Note

Medium Risk
Adds a new endpoint field to the Nexus task proto and threads it through worker dispatch into nexus.info(), which can impact wire compatibility and handler expectations if servers/bridges don’t populate it consistently.

Overview
Exposes the Nexus endpoint name to operation handlers by adding an endpoint field to the NexusTask bridge proto and surfacing it on temporalio.nexus.Info (returned by nexus.info()).

Updates the Nexus worker execution path to pass the polled task’s endpoint into both start and cancel operation contexts, and extends tests to assert the new value (with a guard for time-skipping environments that don’t populate it yet).

Reviewed by Cursor Bugbot for commit 991acb9. Bugbot is set up for automated code reviews on this repo. Configure here.

@Quinn-With-Two-Ns Quinn-With-Two-Ns requested a review from a team as a code owner April 13, 2026 15:49
@Quinn-With-Two-Ns Quinn-With-Two-Ns merged commit 40e75f6 into temporalio:main Apr 14, 2026
31 of 32 checks passed
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.

[Feature Request] Expose Nexus Endpoint in a Nexus Operation Handler

2 participants