Atmos config's `logs.verbose` does nothing
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:
- Specify
logs.verbose = truein your atmos config (like above example) - Run an atmos command.
- No verbose logs.
Screenshots
N/A
Environment (please complete the following information):
N/A
Additional Context
N/A
@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 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 👍
implemented in the latest versions