You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like
Right now, having the action do a run-all plan/apply in a high-level dir outputs a lot of unhelpful text - in our case, we use this action to run a plan on one of our entire repos, which outputs >2000 lines of text, <50 of which are the actual change plan.
It'd be nice to have an only_output_diffs option which would only output everything between Terraform will perform the following actions: and Plan: X to add, X to change, X to destroy.
Describe alternatives you've considered
I can try adding a filter to the output text on our end, but not totally sure how I'd go about doing that since the PR commenting happens in the terragrunt-action script.
EDIT: after poking around a little more, I might be able to add this on our end via an INPUT_POST_EXEC_ env var - would be neat to see this as a built-in feature, though.
Additional context
n/a
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like
Right now, having the action do a
run-all plan/apply
in a high-level dir outputs a lot of unhelpful text - in our case, we use this action to run aplan
on one of our entire repos, which outputs >2000 lines of text, <50 of which are the actual change plan.It'd be nice to have an
only_output_diffs
option which would only output everything betweenTerraform will perform the following actions:
andPlan: X to add, X to change, X to destroy.
Describe alternatives you've considered
I can try adding a filter to the output text on our end, but not totally sure how I'd go about doing that since the PR commenting happens in the
terragrunt-action
script.EDIT: after poking around a little more, I might be able to add this on our end via an
INPUT_POST_EXEC_
env var - would be neat to see this as a built-in feature, though.Additional context
n/a
The text was updated successfully, but these errors were encountered: