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 looking at how to organize projects/stacks with self managed backend. In the docu, the following structure is proposed:
```├── infrastructure
│   ├── index.ts
│   ├── Pulumi.yaml
│   ├── Pulumi.dev.yaml
│   ├── Pulumi.staging.yaml
│   └── Pulumi.prod.yaml
├── myApp
│   ├── index.ts
│   ├── Pulumi.yaml
│   ├── Pulumi.dev.yaml
│   ├── Pulumi.staging.yaml
│   └── Pulumi.prod.yaml
└── ...```
So we use infrastructure to create a vpc and other things in AWS...
Now, for some reason, myApp needs to get a hold of the vpcid output from infrastructure... How would I go about that?

If you're using the self managed backend, you need to name your stacks myApp.dev

To get values from other stacks, you'd use a stack reference 

But all stacks have to be in the same backend 