Document location of SeqCli.json confiugration file

[mloskot]

Although the location is currently fixed as per confirmation in #148 and the current implementation

seqcli/src/SeqCli/Config/RuntimeConfigurationLoader.cs

Line 23 in 9d09f53

Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.UserProfile), "SeqCli.json");

the location is not explicitly stated anywhere in the documentation at https://docs.datalust.co/docs/command-line-client which only says

The API key will be stored in your SeqCli.json configuration file;

It would be very useful if it stated $env:UserProfile/SeqCli.json on Windows and $HOME/SeqCli.json on Linux.

[nblumhardt]

Thanks for the suggestion! A seqcli config path command (or similar) might be a nice way to do this - would that work for you?

[mloskot]

Yes, such a mean to control location of config file would be useful.

I'm not sure how setting the location with seqcli config path would work. Where the location would be persisted?

A more common, from my CLI experience, is to provide either (or both):

• environment variable SEQCLI_CONFIG_PATH (e.g. like Azure CLI does)
• top-level command with option overriding default location of config file

SEQCLI_CONFIG_PATH=~/.config/seq/config.json
seqcli config
seqcli apikey list

seqcli config --config ~/.config/seq/config.json
seqcli apikey list --config ~/.config/seq/config.json

I could try neutralise rust on my C# foo and risk proposing a PR. Which option is preferred, or both?

[nblumhardt]

Ah yes, I see the problem with seqcli config path :-) 👍

Thanks for the offer of help. Perhaps we could start with SEQCLI_CONFIG_PATH, since it seems like it would be least disruptive given the current shape of the codebase?

[mloskot]

@nblumhardt Here is my first stab at this in #400