-
Notifications
You must be signed in to change notification settings - Fork 3
Milestone
Description
Is there an existing issue?
- I have searched the existing issues
Description
No response
Steps to Reproduce
- Run one of the linter or validation workflows in this repo with a change that will force an error to occur.
- Observe minimal details in the workflow when an error occurs.
Expected Behavior
When the linter in terraform-validate.yml encounters an error on things like terraform fmt, it should output the details of the linter error rather than a generic error.
It seems like this is happening because we (correctly) do not run any steps with verbose output in the default workflows. Probably the best way to make this happen is to add a 'debug' option to terraform-validate.yml so that affected contributors could use it to re-run the workflow with more verbose output. But anything that makes it easy to get more details when there are workflow errors would suffice.
Anything else?
No response
Copilot
Metadata
Metadata
Assignees
Labels
No labels