feat(ocap): support multiple providers of a capability type - #50
Merged
Conversation
A published capability's name was both its identity and the only key a consumer could bind to, so exactly one workload could ever satisfy a given name. Separate the two: `name` stays the implementation's own identity and `implements` lists the capability types it satisfies, so dev.edera/foo may implement dev.edera/bar alongside other providers. Selection among them is by `priority` (higher wins), with `provider` on a consume pinning one implementation instead. The pin binds late, so a providing workload may restart or move zones without invalidating it. ObjectCapabilitySpec.receives is replaced by a repeated message field to carry the pin. It is renamed to `consumes` rather than reusing the name on a new tag: WIRE_JSON compatibility requires a deleted field's name to stay reserved, and protoc forbids reusing a reserved name. Tag 2 and the name `receives` are both burned. ObjectCapabilityInfo reports implements/priority for discovery, and DialObjectCapabilityStart carries the pin for direct callers.
|
The latest Buf updates on your PR. Results from workflow Buf CI / buf (pull_request).
|
azenla
approved these changes
Aug 11, 2026
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
2 participants
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.
A published capability's name was both its identity and the only key a consumer could bind to, so exactly one workload could ever satisfy a given name. Separate the two:
namestays the implementation's own identity andimplementslists the capability types it satisfies, so dev.edera/foo may implement dev.edera/bar alongside other providers.Selection among them is by
priority(higher wins), withprovideron a consume pinning one implementation instead. The pin binds late, so a providing workload may restart or move zones without invalidating it.ObjectCapabilitySpec.receives is replaced by a repeated message field to carry the pin. It is renamed to
consumesrather than reusing the name on a new tag: WIRE_JSON compatibility requires a deleted field's name to stay reserved, and protoc forbids reusing a reserved name. Tag 2 and the namereceivesare both burned.ObjectCapabilityInfo reports implements/priority for discovery, and DialObjectCapabilityStart carries the pin for direct callers.