This message was deleted.

Pulumi looks for the program in the current directory. But you can tell it to find the config file elsewhere with the

--config-file

parameter. So, you can run

pulumi up --stack vm --config-file ./../Pulumi.vm.yaml

FROM the stacks/vm folder.

Interesting. But if I have to do it this way, I might as well just have two distinct projects.

That is generally the model used. Can you explain the use-case that is driving you towards wanting a single project for what I’m guessing are two fundamentally (substantially?) different stacks?

What is driving me is not a use case, but a misunderstanding of terminology. I though that a stack was a collection of resources (like in CloudFormation), and that a project was a collection of stacks that together comprise an application. But it appears that a stack is more like an environment (as in staging, test, dev, prod etc.), and a project is the combination of all of the environments. Thanks a lot for clearing this up for me, @witty-candle-66007.

Yes, the terminology can be a bit confusing at times given the same terms are used in other non-pulumi contexts in different ways. If you haven’t already found these docs pages, they’ll probably help further: • https://www.pulumi.com/docs/intro/concepts/ • https://www.pulumi.com/docs/intro/concepts/project/ • https://www.pulumi.com/docs/intro/concepts/stack/

Yes-yes, thank you. I understand now that stacks are instances of a project; stacks are not components of a project.