[ribugent]

Related Issue

Fixes #84

Description

On a self-hosted runner, the node binary isn't in the path, making the wrapper run fail.

In the related issue, there are several workarounds:

• Adding the node binary to the path
• Setting up the node before running Terraform

In my company, we have a shared workflow(using this action) that might run on GitHub-hosted runners or self-hosted runners, and I was hesitant to add a hack.

Looking for a solution I thought it would be nice to run the wrapper using the same node binary as this action does, so I decided to patch the first line of the wrapper to replace the #!/usr/bin/env node shebang with the full path of action node which can be found at process.argv[0].

I tested on my fork using a linux runners (GitHub and self-hosted), and it worked, but I'm unsure what will happen on Windows.

Rollback Plan

• If a change needs to be reverted, we will roll out an update to the code within 7 days.

[hashicorp-cla-app]

All committers have signed the CLA.

[hashicorp-cla-app]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

_{Have you signed the CLA already but the status is still pending? Recheck it.}