Tag commands which require a system account

[philpennock]

It would be very helpful if the commands available could minimally use a standard piece of syntax to mention those which require a system account as opposed to any account. I find myself repeatedly telling people "that error doesn't mean there's a problem, your account just doesn't have access".

Perhaps also if there were a way to decorate in the context with flags, we could mark those contexts (probably manually, or perhaps automatically after a connection test) which are system accounts, and then based on the current context we could elide showing the commands/completions which require a system account.

[ripienaar]

Any suggestions for how that would look, I've also wondered the same but can't think of a obvious yes not annoying way to do this. In general I tried to move all thigns that need system under nats server *

[philpennock]

[system] at the end of the description?

[ripienaar]

Not convinced majority of people can be bothered to read help to spot that. Most run into this pasting stuff from docs etc.

I have started to improve errors though that feels like a more visible place to surface this that everyone will see?

natscli/nats/server_list_command.go

Line 104 in d6aaebb

fmt.Printf("%s status from $SYS.REQ.SERVER.PING, ensure a system account is used with appropriate permissions\n", msg.Header.Get("Status"))

[ripienaar]

made some progress on this, mostly good now, so will close this and will address more as they come up