feat: endpoint groups and attributes#86
Draft
b5 wants to merge 1 commit into
Draft
Conversation
Add cloud-side metadata for client endpoints beyond the existing name: a single `group` and an arbitrary key-value `attributes` map. Both are settable at build time via `ClientBuilder::group` / `attributes` and updatable post-construction via `Client::set_group` / `set_attributes`, mirroring the name API. Attributes use full-replace semantics on each call. Adds matching `SetGroup` / `SetAttributes` RPC messages to the protocol, plus an `endpoint_meta` example that exercises both paths. Group names follow the same 2–128 byte UTF-8 rules as endpoint names. Attribute keys share those rules; values may be empty and are capped at 128 bytes; the map is capped at 128 entries.
|
Documentation for this PR has been generated and is available at: https://n0-computer.github.io/iroh-services/pr/86/docs/iroh_services/ Last updated: 2026-05-17T22:28:50Z |
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.
Add cloud-side metadata for client endpoints beyond the existing name: a single
groupand an arbitrary key-valueattributesmap. Both are settable at build time viaClientBuilder::group/attributesand updatable post-construction viaClient::set_group/set_attributes, mirroring the name API. Attributes use full-replace semantics on each call. Adds matchingSetGroup/SetAttributesRPC messages to the protocol, plus anendpoint_metaexample that exercises both paths.Group names follow the same 2–128 byte UTF-8 rules as endpoint names. Attribute keys share those rules; values may be empty and are capped at 128 bytes; the map is capped at 128 entries.
Description
Breaking Changes
Notes & open questions
Change checklist