atmos icon indicating copy to clipboard operation
atmos copied to clipboard

Atmos config's `logs.verbose` does nothing

Open Gowiem opened this issue 3 years ago • 2 comments

Describe the Bug

When specifying logs.verbose in atmos.yaml, it doesn't do anything. This is my config:

logs:
  verbose: true
  colors: true

The code here is borked: https://github.com/cloudposse/atmos/blob/0a3aca63b72d4b5b3206c5f46552dc49bf8e4a43/pkg/config/utils.go#L325-L337

Expected Behavior

I would expect the verbose logs to show up.

Steps to Reproduce

Steps to reproduce the behavior:

  1. Specify logs.verbose = true in your atmos config (like above example)
  2. Run an atmos command.
  3. No verbose logs.

Screenshots

N/A

Environment (please complete the following information):

N/A

Additional Context

N/A

Gowiem avatar Aug 09 '22 04:08 Gowiem

@Gowiem this functionality is not implemented yet (using the setting from atmos.yaml), and since we can log verbose even before we find and process atmos.yaml config, we implemented it using the ATMOS_LOGS_VERBOSE ENV var

ATMOS_LOGS_VERBOSE=true atmos terraform .....
export ATMOS_LOGS_VERBOSE=true 
atmos  .....

Once it's set to true, atmos will log all the steps it uses to find and parse atmos.yaml, then to find the stack files, then to find and process the component in the stack

aknysh avatar Aug 09 '22 15:08 aknysh

@aknysh Gotcha, yeah, I was just calling it out as it threw me. Hopefully this issue helps others realize it is a missing feature until it is implemented 👍

Gowiem avatar Aug 10 '22 15:08 Gowiem

implemented in the latest versions

aknysh avatar Nov 03 '22 02:11 aknysh