[GH-ISSUE #5714] Add groups in CLI json output #10957

Open
opened 2026-08-05 01:27:52 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @Paulpatou on GitHub (Mar 27, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5714

Is your feature request related to a problem? Please describe.
For internals needs, we use the CLI to retrive and inventory peers on our Netbird network. We cannot use API in our tool's architecture.
Some informations are not included in CLI output. When you have many peers, it made it (almost) useless

Describe the solution you'd like
We use netbird status command with json output. Informations included as peer, PI, status, lastStatusUpdate are fine, but groups are missing to parse them as really usable for us.
We would like to see groups for each peer when creating json.

Describe alternatives you've considered
We know that API give us this information, an array is here and contain groups membership for node but as I say before, we cannot use API in our actual implementation.
Note that we don't need all groups information, just groups membership (groups names listed), but maybe other people may need it ?

Additional context
No additional context here

Originally created by @Paulpatou on GitHub (Mar 27, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5714 **Is your feature request related to a problem? Please describe.** For internals needs, we use the CLI to retrive and inventory peers on our Netbird network. We cannot use API in our tool's architecture. Some informations are not included in CLI output. When you have many peers, it made it (almost) useless **Describe the solution you'd like** We use netbird status command with json output. Informations included as peer, PI, status, lastStatusUpdate are fine, but groups are missing to parse them as really usable for us. We would like to see groups for each peer when creating json. **Describe alternatives you've considered** We know that API give us this information, an array is here and contain groups membership for node but as I say before, we cannot use API in our actual implementation. Note that we don't need all groups information, just groups membership (groups names listed), but maybe other people may need it ? **Additional context** No additional context here
saavagebueno added the feature-request label 2026-08-05 01:27:52 -04:00
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#10957