sparse-intern-71089
03/29/2023, 8:22 AMproud-art-41399
03/29/2023, 8:29 AMLogging into <s3://pulumi.xxx.xxx>
/home/runner/work/_actions/pulumi/actions/v4/webpack:/pulumi-github-action/node_modules/@pulumi/pulumi/automation/errors.js:73
: new CommandError(result));
^
CommandError: code: -2
stdout:
stderr: Command failed with exit code 255: pulumi stack select --stack xxx-xxx-prod --non-interactive
error: PULUMI_ACCESS_TOKEN must be set for login during non-interactive CLI sessions
err?: Error: Command failed with exit code 255: pulumi stack select --stack xxx-xxx-prod --non-interactive
error: PULUMI_ACCESS_TOKEN must be set for login during non-interactive CLI sessions
at Object.createCommandError (/home/runner/work/_actions/pulumi/actions/v4/webpack:/pulumi-github-action/node_modules/@pulumi/pulumi/automation/errors.js:73: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 runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
which didn't suggest the above problem. Only when trying to run Pulumi locally (assuming the IAM role) it showed:
pulumi stack select --stack xxx-xxx-prod
error: read ".pulumi/Pulumi.yaml": blob (key ".pulumi/Pulumi.yaml") (code=Unknown): AccessDenied: Access Denied
status code: 403, request id: V9KQCGMCQS4AYK6Y, host id: nXb8oU+0htao76xHXqi8IJeWWgTsY8kzZsMVAfE6j3A9gk3VR+mH8W92EbtmWIUKS/ltQkJ3hPE=
billowy-army-68599
proud-art-41399
03/29/2023, 3:04 PM.pulumi/Pulumi.yaml
file and when (or more likely why) it was introduced. Seems like my fault in the end that I didn't specify permissions to access this file.