runatlantis/atlantis

Atlantis outputs Timestamp with STDOUT

vignesh-v3 opened this issue · 6 comments

vignesh-v3 commented

atlantis apply outputs timetamp, STDOUT and terraform version

We have recently ugpraded our atlantis to use this image ghcr.io/runatlantis/atlantis:v0.30.0-debian
For some reason we keep getting more verbose that is not needed.

Reproduction Steps

atlantis apply

Logs

08:00:11.551 STDOUT terraform1.9.8: module.wildcard_testnet_discover.ns1_record.record: Modifying... [id=xx]
08:00:11.553 STDOUT terraform1.9.8: module.wildcard_testnet.ns1_record.record: Modifying... [id=xx]
08:00:11.673 STDOUT terraform1.9.8: module.wildcard_testnet_discover.ns1_record.record: Modifications complete after 0s [id=xx]
08:00:11.684 STDOUT terraform1.9.8: module.wildcard_testnet.ns1_record.record: Modifications complete after 0s [id=xx]
08:00:12.096 STDOUT terraform1.9.8: 
08:00:12.096 STDOUT terraform1.9.8: Apply complete! Resources: 0 added, 2 changed, 0 destroyed.
08:00:12.096 STDOUT terraform1.9.8:```
dosubot commented

Hello, @vignesh-v3! I'm here to help you with any bugs, questions, or contributions you have. Let's tackle this together!

To control the verbosity of the output logs in Atlantis, you can use the LogLevelFlag configuration option. This allows you to set the log level to debug, info, warn, or error [1]. However, there isn't specific information available about excluding timestamps or customizing the log format in the current documentation. If the verbosity is due to the new image version, you might want to check if there are any changes in the release notes or configuration that could affect logging, although specific changes in the v0.30.0-debian image regarding logging weren't found in the available data.

To continue talking to Dosu, mention @dosu.

  • 👍1
  • 👎3
brunooon commented

I'm having the same issue after upgrading the image to ghcr.io/runatlantis/atlantis:v0.30.0

vignesh-v3 commented

@brunooon any fix that you've discovered so far?

anryko commented

It's due to the change introduced in terragrunt under "LOG improvements" v0.67.0. Try to rollback your terragrunt to v0.66.9.

  • 👍1
suraj2410 commented

@vignesh-v3 what @anryko worked for me! it was TG and not atlantis change that created this

jamengual commented

I will close base on the comments