Allow configuration via environment variables #449
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#449
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Especially for secrets, it would be very handy to allow configuration via environment variables instead of having them written in plaintext in the configuration file.
This would make deployment via Nix and other deployment tools easier.
Possible implementations would be to read variables like
RPC_SECRET
directly, or allow specifying them as$VARIABLE
in the toml config.Alternatively, allow specifying the secrets in separate files, so that these can be provided separately form the main configuration with something like
rpc_secret_file
instead ofrpc_secret
The last paragraph of this was handled in #466.
Could be nice to also have the admin token be configured by a file, or at least support env vars for just the "sensitive" variables.
It would mean you could check in your config file to git without exposing secrets and could make docker-compose nicer