-
Notifications
You must be signed in to change notification settings - Fork 1.2k
feat(supervisor): expose sandbox name to middleware request context #2771
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -280,6 +280,8 @@ message RequestContext { | |
| string sandbox_id = 2; | ||
| // Workload process that originated the request, when available. | ||
| Process originating_process = 3; | ||
| // Sandbox name that originated the request. | ||
| string sandbox_name = 4; | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please also add Please add assertions for both paths. |
||
| } | ||
|
|
||
| // HttpRequestTarget describes the admitted HTTP destination and request target. | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please clearly document here and in the protobuf field comment that
sandbox_nameis for display and logging only. Names are workspace-scoped and may be reused for different sandbox instances. Consumers must usesandbox_idfor authorization, persistence, durable correlation, and identity.