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

I'm new to Pulumi and currently a bit confused about how `pulumi --cwd &lt;some dir&gt;` is supposed to work.
I wanted to do something like this:
```project root
|_ __main__.py
|_ bootstrap
   |_ __main__.py
   |_ core_deployment.py
   |_ __init__.py```
The bootstrap package has it's own `__main__` file to establish the basic user, group and role for deployments and a privileged user must initially run `pulumi --cwd bootstrap up`. Then for all other deployments, provided bootstrap doesn't need to change, then "regular" users can run `pulumi up` and because the root `__main__` always includes the bootstrap deployment, the state for the stack is always aligned and works just fine provided the regular user doesn't need to destroy the bootstrap state, and then a privileged user is needed again.

BUT using `--cwd` results in the root `__main__` being called regardless (the bootstrap `__main__` is ignored). Even using `cd bootstrap; pulumi up` still results in root `__main__` being called.

What am I missing here?