fix devstack log format

[wdbaruni]

Summary by CodeRabbit

• Refactor
  • Updated logging configuration to set log level earlier in the initialization process
  • Streamlined log configuration logic to ensure consistent log level application

[coderabbitai]

Walkthrough

The changes in the pkg/logger/logger.go file focus on restructuring the ConfigureLogging function's internal logic. The primary modification involves repositioning the ConfigureLoggingLevel(level) call to the beginning of the function, ensuring that the global log level is set before any logging configuration is applied. This change optimizes the logging configuration process by establishing the log level first, which influences subsequent logging behaviors.

Changes

File	Change Summary
pkg/logger/logger.go	Moved ConfigureLoggingLevel(level) call to the start of the ConfigureLogging function; updated function signature.

Poem

🐰 A Logger's Tale of Swift Delight

Hop, hop, through log levels bright,
Rearranged with coding might,
Setting stages before the write,
A rabbit's logic takes its flight! 🌟

Configuration now pure and light 🔍

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fef1951 and 7f5f077.

📒 Files selected for processing (1)

• pkg/logger/logger.go (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• pkg/logger/logger.go

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: testcontainers-suite / tests

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eeceb0f and fef1951.

📒 Files selected for processing (1)

• pkg/logger/logger.go (1 hunks)

🧰 Additional context used

🪛 GitHub Actions: Main Pipeline

pkg/logger/logger.go

[error] 120-120: Spelling error: Unknown word 'leve'

🔇 Additional comments (1)

pkg/logger/logger.go (1)

120-122: LGTM! Good improvement in logging configuration.

Moving the log level configuration to the start of the function is a good change. This ensures the correct log level is set before any logging occurs during the configuration process.

🧰 Tools

🪛 GitHub Actions: Main Pipeline

[error] 120-120: Spelling error: Unknown word 'leve'