SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-07-27 16:32:34 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

"netbird status --json" should return json at NeedsLogin stage #1364

New Issue
Open
opened 2025-11-20 05:29:05 -05:00 by saavagebueno · 5 comments
saavagebueno commented 2025-11-20 05:29:05 -05:00
Owner
Copy Link

Originally created by @Silex on GitHub (Oct 25, 2024).

I'm trying to detect wether netbird was already configured or not.

Right now I'm doing "netbird status | grep NeedsLogin" but it'd be more logical if I could parse the json whatever stage netbird is (needslogin, disconnected, connected).

Originally created by @Silex on GitHub (Oct 25, 2024). I'm trying to detect wether netbird was already configured or not. Right now I'm doing "netbird status | grep NeedsLogin" but it'd be more logical if I could parse the json whatever stage netbird is (needslogin, disconnected, connected).
saavagebueno added the feature-requestclient labels 2025-11-20 05:29:05 -05:00
saavagebueno commented 2025-11-20 05:29:06 -05:00
Author
Owner
Copy Link

@mgarces commented on GitHub (Oct 25, 2024):

so your suggestion is that --json is always available, even when client is not configured?

@mgarces commented on GitHub (Oct 25, 2024): so your suggestion is that `--json` is always available, even when client is not configured?
saavagebueno commented 2025-11-20 05:29:06 -05:00
Author
Owner
Copy Link

@Silex commented on GitHub (Oct 25, 2024):

Yes, with data like { "status": "NeedLogin" } (and additional available info)

@Silex commented on GitHub (Oct 25, 2024): Yes, with data like `{ "status": "NeedLogin" }` (and additional available info)
saavagebueno commented 2025-11-20 05:29:06 -05:00
Author
Owner
Copy Link

@Silex commented on GitHub (Oct 28, 2024):

That said I'm open for a better way of reporting "Client is not configured".

netbird status | grep NeedsLogin works but it does not feel very robust.

My use case is that I'm doing an OpenWRT netbird package with automatic client configuration.

@Silex commented on GitHub (Oct 28, 2024): That said I'm open for a better way of reporting "Client is not configured". `netbird status | grep NeedsLogin` works but it does not feel very robust. My use case is that I'm doing an OpenWRT netbird package with automatic client configuration.
saavagebueno commented 2025-11-20 05:29:07 -05:00
Author
Owner
Copy Link

@rittycat commented on GitHub (Feb 2, 2025):

+1 for this. If you're going to make a flag that provides a machine-readable interface, it needs to be consistent. This is just begging for people to run into errors if they make wrappers (particularly for use-cases like automatic deployment)

@rittycat commented on GitHub (Feb 2, 2025): +1 for this. If you're going to make a flag that provides a machine-readable interface, it needs to be consistent. This is just begging for people to run into errors if they make wrappers (particularly for use-cases like automatic deployment)
saavagebueno commented 2025-11-20 05:29:07 -05:00
Author
Owner
Copy Link

@jbillingredhat commented on GitHub (Nov 19, 2025):

In particular, any attempt to writing our own interfaces to netbird (such as a NetworkManager plugin) would be immensely helped by having a regular interface to the netbird process. Why provide JSON output only in certain circumstances?

@jbillingredhat commented on GitHub (Nov 19, 2025): In particular, any attempt to writing our own interfaces to netbird (such as a NetworkManager plugin) would be immensely helped by having a regular interface to the netbird process. Why provide JSON output only in certain circumstances?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label client feature-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1364
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?