Add broker-facing IFC sessions - #7497
Draft
jmecom wants to merge 2 commits into
Draft
Conversation
Signed-off-by: Jordan Mecom <jm@squareup.com>
Signed-off-by: Jordan Mecom <jm@squareup.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
IfcSessionover the Buzz execution domains in #7349. The broker checks reads withread(resource), non-publishing operations withcall(operation), and publications withpublish(operation, destination, bytes).Publication authorization owns the serialized request, operation name, and destination label. Shared mutable payloads are rejected by the API, so the request cannot change while waiting for the sink. Reads only validate: the session starts with its domain's audience restrictions, and every admitted resource must fit them.
Stacked on #7349 (
jm/buzz-ifc-domain). This is library-only. The broker must authenticate facts, check current membership and destination policy, and execute the complete request bytes that were authorized. Integrity tracking, declassification, and runtime integration are not included.Checked: formatting, strict Clippy, 28 unit tests and 7 doctests across
buzz-ifcandifc-core, including frozen-request and compile-fail regressions. The adversarial follow-up review found no remaining bugs. Repository-widejust ciis still running.