setup-terraform/.changes/unreleased/BUG FIXES-20231027-092614.yaml

kind: BUG FIXES
body: Fixed malformed stdout when wrapper is enabled
time: 2023-10-27T09:26:14.675402-04:00
custom:
  Issue: "367"
Fix output malformed when wrapper enabled (#367) * Fix output malformed when wrapper enabled Presently using a command such as `terraform output -json \| jq` does not work with the wrapper enabled, as it is by default. In order to consume terraform's output having set it up with this Action, it is necessary either to disable the wrapper (`with: terraform_wrapper: false`) or run it in its own Actions step with an explicit `id` (e.g. `id: foo`) so that it can be referred to and consumed (`${{steps.foo.outputs.stdout}}` et al.) in later steps. This seems to be the result of much confusion (issues passim) and is not at all easy (#338) to debug/diagnose and come to the realisation that it's due to the wrapper, or even that such a thing exists. @austinvalle identified the issue as being due to the `@actions/exec` package writing the spawned command to stdout (along with then its actual stdout). This has previously been reported upstream in actions/toolkit#649; I've proposed actions/toolkit#1573 to fix it. This commit aims to address the issue for `setup-terraform` in the meantime by silencing `@actions/exec` and then writing out to stdout & stderr from the listener buffers, which it writes to without this additional logging. Closes #20, #80, #85, #149, #338, and probably more. * add test for stdout with jq * update test name * remove debug lines and add changelog * add additional note about the bug fix to wrapper --------- Co-authored-by: Austin Valle <austinvalle@gmail.com> 2023-10-27 18:05:58 +00:00			`kind: BUG FIXES`
			`body: Fixed malformed stdout when wrapper is enabled`
			`time: 2023-10-27T09:26:14.675402-04:00`
			`custom:`
			`Issue: "367"`