Repository navigation
fix(server): reject reserved annotation keys - #4626
Conversation
Signed-off-by: Eric Curtin <eric.curtin@docker.com>
|
@johntmyers @elezar PTAL when you get a chance, and |
|
/ok to test b6d4e82 |
Compatibility review (advisory)New or updated breaking changes; see the full report for all findings. 1. api-behavior — No explicit risk acceptance found
Review details
Advisory review; publication gates are unchanged. |
|
The restriction is acceptable, we shouldn't be allowing modification of the internal keys. |
TaylorMutch
left a comment
There was a problem hiding this comment.
Reviewed the reserved annotation validation on CreateSandbox and UpdateConfig. The shared early check rejects gateway-owned keys before persistence across the update paths, while preserving gateway writes and ordinary caller annotations. All nine annotation-related tests passed locally against this revision, and PR checks passed.
Summary
Reject
internal.openshell.ai/annotation keys from API callers onCreateSandboxandUpdateConfig.Related Issue
Closes #4533
Changes
validate_caller_annotationsand use it for both RPCs.handle_create_sandbox_inner.annotationsfields in the proto.Testing
cargo test -p openshell-server --lib grpc::, clippy and fmt pass.mise run go:proto:genis a no-op after the comment edit.Checklist