# aws


07/25/2023, 9:05 PM
Greetings, I am using the pulumi/actions@4 to try and deploy C# code from a pre-existing docker container to aws ecs - and some other stuff - but I get errors before that's even a problem: When the github action is running preview against my prod stack I now get
Copy code
Configured range: ^3
/usr/local/bin/pulumi version
Pulumi version 3.76.0 is already installed on this machine. Skipping download
Logging into the Pulumi Cloud backend.

                    : new CommandError(result);
CommandError: code: -2
 stderr: Command failed with ENOENT: pulumi version --non-interactive
spawn pulumi ENOENT
 err?: Error: Command failed with ENOENT: pulumi version --non-interactive
spawn pulumi ENOENT

    at Object.createCommandError (/home/runner/work/_actions/pulumi/actions/v4/webpack:/pulumi-github-action/node_modules/@pulumi/pulumi/automation/errors.js:77:1)
    at Object.<anonymous> (/home/runner/work/_actions/pulumi/actions/v4/webpack:/pulumi-github-action/node_modules/@pulumi/pulumi/automation/cmd.js:76:1)
    at Generator.throw (<anonymous>)
    at rejected (/home/runner/work/_actions/pulumi/actions/v4/webpack:/pulumi-github-action/node_modules/@pulumi/pulumi/automation/cmd.js:19:1)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
Previously it was on 3.75.0, and I got complaints, so I added the version 3.76.0, but clealrly, that doesn't help. What do I do with that error? IS there a way to get mroe info from the githuh action? So - this stack has worked before until a couple of weeks ago, but node versions are expiring left, right and centre, so I had to bump some versions. I intermittently had green deployments - no errors - but it literally didn't deploy anything, so I'm re-evaluating all my life choices. This thouugh - is worse. A logfile woudl be fantastic with some alleged errors would be nice.