fix: Log to stderr per default

[mss]

what

• Sync the default value for logs.file with the one shipped in atmos.yaml.

why

• atmos behaves different without an atmos.yaml file than with the one shipped per default.
• It avoids the logging bug in Weird escape code issues with v1.158.0 #1026.

references

• Works around (but does not fix) Weird escape code issues with v1.158.0 #1026.

Summary by CodeRabbit

• Chores
  • Updated the default logging destination from standard output to standard error, which may change where logs are visible if no specific log file is provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

This update changes the default logging output for Atmos. The persistent flag in the CLI command and the corresponding config variable have been updated to use "/dev/stderr" instead of "/dev/stdout". No changes have been made to the underlying logging logic; only the default destination for logs has been modified.

Changes

Files	Change Summary
cmd/root.go, pkg/config/config.go	Changed default log file destination from "/dev/stdout" to "/dev/stderr" in CLI flag and config.

Assessment against linked issues

Objective	Addressed	Explanation
Weird escape code issues with v1.158.0 [#1026]	✅

Possibly related PRs

• Logs validation on root level #946: Modifies the logs-file flag in cmd/root.go, indicating a related change in logging default behavior.

Suggested labels

patch

Suggested reviewers

• osterman
• aknysh

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 300ca0f and 596112f.

📒 Files selected for processing (2)

• cmd/root.go (1 hunks)
• pkg/config/config.go (1 hunks)

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

• GitHub Check: Summary

🔇 Additional comments (2)

cmd/root.go (1)

186-186: LGTM! The default logging output is now synchronized.

The change aligns the default value with the default atmos.yaml configuration.

Let's verify that this change doesn't affect existing logging behavior:

✅ Verification successful

🏁 Script executed:

#!/bin/bash
# Search for any custom log file configurations in the codebase
rg -A 2 "logs-file|logs.file" --type yaml

Length of output: 6336

---

Default logging behavior verified:
The output from our search confirms that the atmos configuration files document the use of the logs-file flag with the same default (/dev/stderr) as set in cmd/root.go. There’s no evidence that the change inadvertently affects existing logging behavior.

pkg/config/config.go (1)

78-78: LGTM! The default config is now consistent.

The change ensures that the default CLI configuration matches the persistent flag's default value.

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • 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 or @auto-summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @auto-title anywhere in the PR title to generate the title automatically.

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.

[osterman]

@mss looks like snapshots need to be updated for a few tests.

https://github.com/cloudposse/atmos/actions/runs/13159121518/job/36723834716?pr=1028

Just run the following, replacing <failing test> with the test that needs a new snapshot.

go test ./tests -v -run 'TestCLICommands/<failing test>' -timeout 2m -regenerate-snapshots

[osterman]

works around (but does not fix) #1026.

Re: the "does not fix" part, is the issue when we write to /dev/stdout that the TTY is not rendering ansi?

[mss]

works around (but does not fix) #1026.

Re: the "does not fix" part, is the issue when we write to /dev/stdout that the TTY is not rendering ansi?

Yes, as soon as the logging goes to stdout weird escape sequences appear. I guess the logging library (wasn't that changed recently?) is fighting with the regular colored output.

[osterman]

@mss will fix this today in #1029