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

hello Puluminati. I'm wondering if/how others are handling the dynamic multi-tenancy use case with Pulumi. I need to programmatically spin up and tear down client environments in response to e.g. sign-ups, ideally without committing any stack yml files to a repo. In my browse of the docs I couldn't find a blessed pattern for this. anyone got some XP here?

I would start by checking out Automation API, if you are not familiar.

<https://www.pulumi.com/docs/guides/automation-api/>

We also have a channel for it, if you want :slightly_smiling_face:

<#C019YSXN04B|automation-api>

thanks Simen. of course by multi-tenancy I actually meant single-tenancy :man-facepalming:. looks like automation API is what I need