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

[Silex]

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).

[mgarces]

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

[Silex]

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

[Silex]

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.

[rittycat]

+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)