-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use machine readable output for plan and apply #9
Comments
Tried this. The machine readable output is not as verbose, and leaves out context info, e.g. the attributes that make up a resource are not shown unlike with the human readable output. Need to decide whether users would be put off by this before implementing. |
Would you consider multiple levels of verbosity? I have found that developers like to see more output in there pipelines where as production pipelines do not need so much. |
@davidjeddy I'm not sure what you're proposing. Terraform already supports a https://developer.hashicorp.com/terraform/internals/machine-readable-ui |
was hoping the output of PUG itself could have levels. While TF TF_LOG was thinking PUG could have PUB_LOG for output of PUG specific runtime messages. |
Pug has logging and levels already. Press |
Internally use machine readable output from plan and apply, converting into human readable output while streaming. Parse former output to extract metadata.
The text was updated successfully, but these errors were encountered: