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

What is the recommended way of organising the pulumi code? Right now I am doing this (in Go). All this does is setup EKS cluster:

```- core
- aws-eu-west-1
  - Pulumi.yaml
  - Pulumi.dev.yaml
  - Pulumi.prod.yaml
  - main.go // which just imports stuff from `core` and passes required config
- aws-eu-west-2
  - Pulumi.yaml
  - Pulumi.dev.yaml
  - Pulumi.prod.yaml
  - main.go
...```
• I believe above creates one Pulumi project per region. 
• to setup / modify cluster, I cd into the region directory and run relevant pulumi commands