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 think you would just compartmentalize this kinda like this:

1. Deploy transient pre-production stack (maybe generate a stack name with the build id or something)
2. Run e2e tests
3. Destroy pre-production stack
4. Deploy production stack

I think if you are uploading your build artifacts with Pulumi than you might want to pull that portion out into a separate Pulumi project so that it can deployed independently of production/pre-production.

So that tearing down pre-production doesn't mean tearing down those artifacts.

Sound legit :slightly_smiling_face: I'm not sure we want to dispose the pre-production environment every time

Gotcha, so yea whatever works for you guys obviously but something like that is how I would do it

I think that sounds like a reasonable approach, and possible to implement a multi-stage workflow like this with automation api.

Do you have any specific questions that I can help with?