use debug logs during create project status

[motatoes]

Summary by CodeRabbit

• Style
  • Reduced the visibility of certain log messages related to project creation, so they now appear only in debug mode instead of standard logs.

[coderabbitai]

Walkthrough

The logging level for messages about project creation in the Parse function of the Atlantis configuration generator was changed from Info to Debug. This affects three log statements related to project handling and does not alter any other logic or control flow in the code.

Changes

File(s)	Change Summary
libs/digger_config/terragrunt/atlantis/generate.go	Changed three log statements from Info to Debug level in the Parse function.

Poem

The logs once shouted, "Project made!"
Now quietly, in debug, their messages fade.
Less noise in the night, more peace in the day,
For only the curious will see what they say.
🐰✨

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/use-debug-logs

---

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

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @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.

[delve-auditor]

✅ No security or compliance issues detected. Reviewed everything up to e4e4fd6.

Security Overview

• 🔎 Scanned files: 1 changed file(s)

Detected Code Changes

Change Type	Relevant files
Enhancement	► BaseLogging.ts     Add debug logging for project status creation

Reply to this PR with @delve-auditor followed by a description of what change you want and we'll auto-submit a change to this PR to implement it.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

libs/digger_config/terragrunt/atlantis/generate.go (1)

808-814: Log level lowered to Debug – ensure consistency with “Updated project” log

Switching the “Created project” message from Info to Debug will reduce noise, 👍.
However, the corresponding “Updated project” message (line 800) is still logged at Info. If the intent is to keep creation messages quiet, the update path probably deserves the same treatment for symmetry and to avoid an unintentionally lopsided log stream.

- slog.Info("Updated project", "path", terragruntPath)
+ slog.Debug("Updated project", "path", terragruntPath)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8668ee1 and e4e4fd6.

📒 Files selected for processing (1)

• libs/digger_config/terragrunt/atlantis/generate.go (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (11)

• GitHub Check: Build
• GitHub Check: Build
• GitHub Check: Build
• GitHub Check: Build
• GitHub Check: Build
• GitHub Check: Build
• GitHub Check: Build
• GitHub Check: Security Check
• GitHub Check: Build
• GitHub Check: Build
• GitHub Check: Build

🔇 Additional comments (1)

libs/digger_config/terragrunt/atlantis/generate.go (1)

846-849: Debug-level HCL-project creation log looks good

The change to slog.Debug here matches the new logging granularity and keeps output consistent with the branch above. No further action required.

[greptile-apps]

PR Summary

Modified logging levels in Terragrunt parser to reduce verbosity by downgrading project creation status logs from Info to Debug level.

• Changed log level in libs/digger_config/terragrunt/atlantis/generate.go from Info to Debug for project creation status, improving operational clarity by reducing non-critical log noise

_{1 file reviewed, no comments
Edit PR Review Bot Settings | Greptile}