feat: Add environment variable SEQCLI_CONFIG_FILE for custom config location

[mloskot]

This allows users to specify custom location of config file.

For example

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

Closes #399

Tests result

Run it on Linux (Ubuntu 25.04) with .NET 9.0

$ cd test/SeqCli.Tests
dotnet test --filter SeqCli.Tests.Config
Restore complete (1.1s)
  Roastery succeeded (3.6s) → /home/mloskot/cadcorp-cloud/_workshop/seq/seqcli/src/Roastery/bin/Debug/net9.0/Roastery.dll
  SeqCli net9.0-windows succeeded (5.2s) → /home/mloskot/cadcorp-cloud/_workshop/seq/seqcli/src/SeqCli/bin/Debug/net9.0-windows/seqcli.dll
  SeqCli net9.0 succeeded (5.2s) → /home/mloskot/cadcorp-cloud/_workshop/seq/seqcli/src/SeqCli/bin/Debug/net9.0/seqcli.dll
  SeqCli.Tests net9.0-windows succeeded (0.7s) → bin/Debug/net9.0-windows/SeqCli.Tests.dll
  SeqCli.Tests net9.0 succeeded (0.9s) → bin/Debug/net9.0/SeqCli.Tests.dll
[xUnit.net 00:00:00.01] xUnit.net VSTest Adapter v3.1.1+bf6400fd51 (64-bit .NET 9.0.6)
[xUnit.net 00:00:00.17]   Discovering: SeqCli.Tests
[xUnit.net 00:00:00.00] xUnit.net VSTest Adapter v3.1.1+bf6400fd51 (64-bit .NET 9.0.6)
[xUnit.net 00:00:00.37]   Discovered:  SeqCli.Tests
[xUnit.net 00:00:00.15]   Discovering: SeqCli.Tests
[xUnit.net 00:00:00.45]   Starting:    SeqCli.Tests
[xUnit.net 00:00:00.68]   Finished:    SeqCli.Tests
[xUnit.net 00:00:00.59]   Discovered:  SeqCli.Tests
[xUnit.net 00:00:00.71]   Starting:    SeqCli.Tests
[xUnit.net 00:00:00.88]   Finished:    SeqCli.Tests
  SeqCli.Tests test net9.0 succeeded (2.8s)
  SeqCli.Tests test net9.0-windows succeeded (3.1s)

Test summary: total: 6, failed: 0, succeeded: 6, skipped: 0, duration: 3.1s
Build succeeded in 15.0s

[KodrAus]

Thanks for working on this @mloskot! I just had one comment on the way we choose the config file path.

[KodrAus]

Thanks for working on this @mloskot! This looks good to me

[mloskot]

Thanks for the reviews and approval @KodrAus

[KodrAus]

The build failure here is probably unrelated to your changes. I'll see if I can track down what's going on. It looks like we're failing to stand up a Seq container in the GitHub Action

[nblumhardt]

Just a quick note to let you know this one isn't forgotten; it intersects with some other work we have in progress so we'll need to merge in a couple of hops to keep things lined up :-)

[mloskot]

@nblumhardt No worries here, I appreciate the notification.

[nblumhardt]

Thanks for pushing this ahead @mloskot!

There was a pretty heavy conflict between this and the --storage argument added to support the new forwarder commands, but the combination of approaches works nicely.

The variable name became SEQCLI_STORAGE_PATH, and this is consulted if the --storage argument isn't supplied. This also guides the CLI to additional storage locations nested under that path, for example the forwarder's buffer files.

I didn't go to too much trouble updating command-specific docs in the README, as we generate these from the command definitions during build and will need to update them in bulk once we're through the rest of the forwarder work.

If you spot anything I made a mess of, please let me know :-) --- cheers!

[mloskot]

@nblumhardt Thanks for the explanation.

I did quick build of the latest dev branch and tests succeed.

I've also tried the SEQCLI_STORAGE_PATH location with the https://datalust.co/docs/command-line-client example commands, and it generally seems to work:

but there is something peculiar going on about the connection.apiKey setting:

and

I assume the dev is a work in progress, so not opening an issue.

[nblumhardt]

Thanks for the note; a bit of churn currently going on, but we should have this sorted out today 😅 👍