The CLI flag list is growing (--profile, --region, --skip-metrics, --skip-sagemaker, --skip-eks, --skip-k8s, --skip-costs, --kubeconfig, --kube-context, --exclude-tag, --min-uptime-days, --prom-url, --prom-endpoint, etc). Most runs use the same configuration.
Add support for a config file (e.g., ~/.config/gpuaudit/config.yaml or .gpuaudit.yaml in the project root) so users can persist their common settings.
Considerations:
- CLI flags should override config file values
- Support both global (
~/.config/gpuaudit/config.yaml) and local (.gpuaudit.yaml) configs, local takes precedence
- YAML or TOML format
gpuaudit init command to generate a starter config
The CLI flag list is growing (
--profile,--region,--skip-metrics,--skip-sagemaker,--skip-eks,--skip-k8s,--skip-costs,--kubeconfig,--kube-context,--exclude-tag,--min-uptime-days,--prom-url,--prom-endpoint, etc). Most runs use the same configuration.Add support for a config file (e.g.,
~/.config/gpuaudit/config.yamlor.gpuaudit.yamlin the project root) so users can persist their common settings.Considerations:
~/.config/gpuaudit/config.yaml) and local (.gpuaudit.yaml) configs, local takes precedencegpuaudit initcommand to generate a starter config