fix: config log level

[thushan]

wires logging.level from config.yaml to the runtime logger (previously parsed but ignored); precedence is OLLA_LOGGING_LEVEL env > config file > default, invalid values warn and fall back rather than crash; also moves flag.Parse() out of init(), fixing go test on the main package.

Summary by CodeRabbit

• New Features

  • Logging levels can now be configured and applied at runtime.
  • Supported log levels are validated case-insensitively.

• Bug Fixes

  • Invalid or empty logging settings now safely fall back to the default level.
  • Test commands no longer process application command-line flags unexpectedly.
  • Logging remains available if applying a configured level fails.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 8122e75c-166f-45ba-92ef-2eae0393f4fa

📥 Commits

Reviewing files that changed from the base of the PR and between 6e51ca0 and 67cb383.

📒 Files selected for processing (4)

• internal/logger/logger.go
• internal/logger/logger_test.go
• main.go
• main_test.go

---

Walkthrough

The change adds case-insensitive log-level validation, defers flag parsing until main, and resolves the configured runtime log level after configuration loading. The application replaces the bootstrap logger when required and retains it if replacement fails.

Changes

Runtime logging

Layer / File(s)	Summary
Log-level validation internal/logger/logger.go, internal/logger/logger_test.go	Adds IsValidLevel for supported level names and tests valid, case-insensitive, empty, and unsupported values.
Startup initialisation main.go	Moves flag parsing into main and manages bootstrap logger cleanup through a replaceable handle.
Runtime logger resolution main.go, main_test.go	Resolves configured levels after configuration loading, warns for invalid values, replaces the logger when needed, and tests valid, empty, and invalid configurations.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
  participant main
  participant Configuration
  participant resolveRuntimeLogLevel
  participant IsValidLevel
  participant RuntimeLogger
  main->>Configuration: load configuration
  main->>resolveRuntimeLogLevel: resolve configured level
  resolveRuntimeLogLevel->>IsValidLevel: validate level
  IsValidLevel-->>resolveRuntimeLogLevel: return validity
  resolveRuntimeLogLevel-->>main: return effective level
  main->>RuntimeLogger: rebuild when level differs
  RuntimeLogger-->>main: return logger and cleanup handle

Loading

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the primary change: fixing configuration-based log-level handling.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/config-log-level

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[thushan]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.