This message was deleted.

Is it a local stack? If you're not logged into Pulumi then it'll be a local stack; your CI won't have access to it. Maybe you need to set up the Pulumi app key, or run

pulumi login

? When you say "All the stack-files are present in the code base", do you mean the Pulumi.<stackName>.yaml file? That's not the stack file; the stack file will be in the Pulumi app, S3, or something like that.

So yea, was referring to the YAML file, the configuration. We provide a pulumi auth key to the pipeline, so it should have access to whatever is present in Pulumi cloud, no?

If it can't find the stack, then the name you're passing to

--stack

doesn't match the name in the Pulumi app. The config files aren't relevant for that error. Maybe there's a missing quote, or a missing org name, or something? You'll have to debug the invocation, Maybe you could put

pulumi stack ls

in your CI pipeline / workflow, just before the command that isn't working, to see what stacks exist. Perhaps the stack exists but isn't available to the user that owns the auth key that the pipeline is using?

Alright, so I realised I had indeed missed something. We had planned earlier that we wanted automatic access to new stacks for the CI token, which I thought had been implemented, but it hadn't, so obviously it didn't have access. So yeah, I think for now all is good :D