node-windows | Windows support for Node.JS scripts | Command Line Interface library

So the way I ended up doing this is instead just pass my codeclient variable through the scriptOptions of node-windows, and then using that in my node application to have dotenv load a specific env file. It's more simple really.

The only issue I had with the approach is that node-windows would fail with my numerical codeclient, always assuming it's a number type instead of a string (node-windows tries to call String.split() on it later). I had to append the underscore in front to force it as a string.

Script to create the Windows service with node-windows:

The launch_template for aws_eks_node_group was introduced in version 3.3.0 of the Terraform AWS Provider.

Make sure that you use at least version 3.3.0 of the aws provider (see docs for terraform 0.11):

I have fixed it. The error is related to the way that Inno Setup creates a temporary directory and executes inside that directory. Basically I needed to have set the WorkingDir parameter, which as you can see above I did not set properly.

All credit to Martin Prikryl and Corey Butler for pointing me in the right direction.

The prototype for ShellExec is as follows:

function ShellExec(const Verb, Filename, Params, WorkingDir: String; const ShowCmd: Integer; const Wait: TExecWait; var ErrorCode: Integer): Boolean;

Found here

I have amended my code to the following:

You have two problems:

1. Ordering

   An ARG outside the FROM block is only accessible in the FROM line itself. In this case, as you don't need to use the --build-arg as part of the FROM, move it inside:

It was my mistake and after updating the path as below, it worked. Missed one slash on last.