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

We have a Pulumi Application with Multiple Stacks

- Dev
- Staging
- Prod

We are likely to have about `20` stacks for a pulumi repo.

All of these above shares the same code expect configuration.
```
Config
	Dev
	Staging
	Prod
```
When there is a config change in `Dev` `config`, we would like to deploy only to `Dev` and to no other ENV.

Within the CI we can identify which files have changed with something like this <https://stackoverflow.com/a/424142/19407> and then deploy only to those ENV, which is somewhat Hacky IMO.

Is there a better way to solve this? How is everyone else solving this issue?

Thanks