Support License Key and Default API Keys on Startup

[p-liubchenko]

It would be beneficial to provide the ability to supply the Seq license key and default API keys during Docker container startup.

Current Behaviour:

The license key must be manually entered after deployment.
API keys need to be created manually via the UI.

Proposed Solution:

Support an environment variable (e.g., SEQ_LICENSE_KEY) for license key provisioning.
Allow default API keys to be defined during initialization (via env vars or init scripts).

Benefits:

Fully automated deployments without manual post-setup steps.
Consistent configurations across environments.
Improved integration with CI/CD pipelines.
This would simplify automated deployments and align with best practices for containerized environments.

[nblumhardt]

Thanks for the suggestion!

Currently, license setup is automated via seqcli license apply, which works against the external container API. We're keen to assemble a solution for this scenario which is able to leverage seqcli, since it's capable of a much broader range of setup tasks than environment variables ever could, so the ideal result for us would be something like an init script with seqcli on the path and configured, which would run in a context with API access available.

The script itself, and any resources like license certificates that are needed, could be mounted using techniques like K8s configmaps, etc.

Keen to come up with a plausible way we could do this, though as we're in the final stages of the 2025.1 release it may be a while before we're able to dig in deeper.

Thanks again!

[p-liubchenko]

Ok, I totally missed init script. that's all I need for now.