NEED HELP big time (paying customer of Pulumi Cloud) - here is the Github Issue I created on the

pulumi/actions

repo that starts it off. I updated it w latest testing. The gist is: • have 3 projects inside of a monorepo for our Infrastructure • each project is within its own folder at the root and contains its own

Pulumi.yaml

and

Pulumi.dev.yaml

(folder name = project name, e.g.

./base

contains

kettleos/base

project) • all projects are namespaced to be part of our org (

kettleos

) • last successful run of

pulumi/actions@v3

in a job was Oct 26, 2022 • first failed run of

pulumi/actions@v3

in a job was Nov 14, 2022 • there were no runs in between those dates Problem: despite configuring the

stack-name

param to the job as

kettleos/{project}/{stack}

(e.g.

kettleos/base/dev

) the command run throws an error that the Stack Cannot be found with the error output missing the Project Name in the output, e.g.:

Logging into the Pulumi Service backend.
Error: code: -2
 stdout: 
 stderr: Command failed with exit code 255: pulumi stack select --stack kettleos/base/dev --non-interactive
error: no stack named 'kettleos/dev' found
 err?: Error: Command failed with exit code 255: pulumi stack select --stack kettleos/base/dev --non-interactive
error: no stack named 'kettleos/dev' found

Please add a step before the actions run to list the stacks. Is the access token you’re using associated with the org in question?

Also, there should be no project in the stack name.

--stack kettleos/dev

why did it work before and it stopped?

Check the workflow code.. did it change?

thanks @billowy-army-68599 and @little-cartoon-10569 trying to respond as best I can and get info as quick as I can

Could be a few reasons, but my guess is that more than likely the user associated with access token no longer has access to the org?

prior to creating the issue, we were only pinned to

action@3

Have you revoked that token?

do the access tokens expire?

Okay well some steps to take: • verify the token is still valid • run a stack list against the project inside the action • Verify the stack name is correct

wait, it could be the user was removed from access - we have 2 separate monorepos (one for infra and one for apps). It may be the access token in the infra was from a previous user

run pulumi stack ls as a job step

it was the access token

@square-laptop-45713 Very glad you got a resolution! 🥳 Would it be okay with you if I close the issue?

I closed it already @worried-rain-74420

Awesome, thanks!