No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

It sounds like you are not logged into the same pulumi state backend that your CMS Provider uses.

thanks for your reply. the cms does not use the pulumi backend for state management. Insted they are stored locally inside the project.

the weird thing is, that there are 2 other pulumi stacks in the same project and I don't have that error with them...they just work

can you see the stack in your state directory?

there should be a file for each stack in the `stacks` directory inside your state folder

ok so have you confirmed that you are logged into that directory?
```pulumi login file://&lt;path&gt;```

I'm afraid I can not answer this question. afaik the cms does not use any form of pulumi login :confused: also I think it's not the issue as I can run pulumi commands against other stacks in that same repo

Thats actually the point that drives me crazy. Why is it working with the other stacks? what may be the different? (I don't see any obvious diffrents in the state files and their structure)

well they must login somehow to specify a custom state location. That is either done with the command I mentioned in CLI, or an environment variable, or in the pulumi project file

My concern was maybe you are logged into another project or state backend that has the same stack names as those other 2 but not `dev`

I will have to talk to the devs to get some more input on how they do things :confused:

until then, thank you so much for your suggestions :heart: I may be back tomorrow