Auto-provisioned channels and in/out ports - #6
Merged
Conversation
rnortman
force-pushed
the
inout-ports-auto-channels
branch
from
July 29, 2026 11:55
2a711fb to
a2cfcb6
Compare
Channels can be "auto" or "anonymous" channels which come into being not with a separate spec and ACLs but because two component ports are connected to one another. ACLs are automatically granted and depth is automatically computed. If a name is given, it's a normal named channel; otherwise it's a private anonymous channel given only a UUID which is not discoverable by any means except to the ports connected to it. This also adds In/out ports, for a component that relies on listening to its own outputs (e.g. for timers/scheduling). This is one port that's both an input and an output and must be connected to the same channel. It automatically gets an anonymous local channel there if the operator doesn't connect something different.
rnortman
force-pushed
the
inout-ports-auto-channels
branch
from
July 29, 2026 12:18
a2cfcb6 to
940b02d
Compare
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.
Two things:
Channels can be "auto" or "anonymous" channels which come into being not with a separate spec and ACLs but because two component ports are connected to one another. ACLs are automatically granted and depth is automatically computed. If a name is given, it's a normal named channel; otherwise it's a private anonymous channel given only a UUID which is not discoverable by any means except to the ports connected to it.
This also adds In/out ports, for a component that relies on listening to its own outputs (e.g. for timers/scheduling). This is one port that's both an input and an output and must be connected to the same channel. It automatically gets an anonymous local channel there if the operator doesn't connect something different.