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

recommended workflow for when a devops team has multiple engineers working on pulumi at the same time and we want to avoid destroying WIP of each other will it reaches `main` branch?

I believe a possible approach is a GCP project per developer and, each one has its own stack?

Definitely a stack (or more) per developer is a reasonable way to go, if you'll be destroying resources and actively making changes that you're not all consulting each other on. You don't necessarily need projects per developer.

If that process works for you, then stacks are the tool for the job. It doesn't sound like a good development model though: if you're all working on one product, wouldn't planning and development as a team be better? Either pairing / mobbing, or just planning development areas so that you have no risk of destroying each others' resources?

hey thanks for answer, we are in different timezones so pair programming is not always an option.

Yep, then planning + stacks should handle things well for you.