Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

tailcfg: document peer node capability #11379

Closed
wants to merge 2 commits into from
Closed

tailcfg: document peer node capability #11379

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
53e0a6a
tailcfg: document peer node capability
clairew Mar 8, 2024
986f5c1
tailcfg: document use of CapMap for peers
sailorfrag Apr 3, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 10 additions & 0 deletions tailcfg/tailcfg.go
View file
Open in desktop
Expand Up @@ -338,6 +338,16 @@ type Node struct {
// CapMap with an empty value.
//
// See NodeCapability for more information on keys.
//
// Metadata about nodes can be transmitted in 3 ways:
// 1. MapResponse.Node.CapMap describes attributes that affect behavior for
// this node, such as which features have been enabled through the admin
// panel and any associated configuration details.
// 2. MapResponse.PacketFilter(s) describes access (both IP and application
// based) that should be granted to peers.
// 3. MapResponse.Peers[].CapMap describes attributes regarding a peer node,
// such as which features the peer supports or if that peer is preferred
// for a particular task vs other peers that could also be chosen.
CapMap NodeCapMap `json:",omitempty"`

// UnsignedPeerAPIOnly means that this node is not signed nor subject to TKA
Expand Down