When running without a config.yaml file (common for env-var-only deployments and Docker), five identical messages are logged at Info level on every startup:
{"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"}{"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"}{"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"}{"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"}{"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"}
This comes from pkg/config and is confusing because:
It says "Failed" which implies an error, but the app works fine without a config file
It appears 5 times (presumably once per config key lookup)
It's at Info level, polluting normal startup logs
Fix
Either:
Change these to Debug level so they only appear when DEBUG=true
Check for config file existence once at startup and only log one message
Suppress the message entirely when no config file is expected (env-var-only mode)
Category
Nice-to-have. Cosmetic but affects operational clarity.
## Bug
When running without a `config.yaml` file (common for env-var-only deployments and Docker), five identical messages are logged at Info level on every startup:
```json
{"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"}
{"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"}
{"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"}
{"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"}
{"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"}
```
This comes from `pkg/config` and is confusing because:
1. It says "Failed" which implies an error, but the app works fine without a config file
2. It appears 5 times (presumably once per config key lookup)
3. It's at Info level, polluting normal startup logs
## Fix
Either:
1. Change these to Debug level so they only appear when DEBUG=true
2. Check for config file existence once at startup and only log one message
3. Suppress the message entirely when no config file is expected (env-var-only mode)
## Category
Nice-to-have. Cosmetic but affects operational clarity.
Understood — removing file-based configuration entirely. Env vars only, no Viper, no config.yaml. Will implement after the current delivery engine worker pool rework completes (same branch).
Understood — removing file-based configuration entirely. Env vars only, no Viper, no config.yaml. Will implement after the current delivery engine worker pool rework completes (same branch).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Bug
When running without a
config.yamlfile (common for env-var-only deployments and Docker), five identical messages are logged at Info level on every startup:This comes from
pkg/configand is confusing because:Fix
Either:
Category
Nice-to-have. Cosmetic but affects operational clarity.
let’s get rid of file-based configuration entirely.
Understood — removing file-based configuration entirely. Env vars only, no Viper, no config.yaml. Will implement after the current delivery engine worker pool rework completes (same branch).