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! Making my way through the documentation and trying to architect a solution here- I am moving from a Terraform based setup and trying to understand what Environments are at the moment. I have individual buckets/DNS/K8S namespaces per customer and trying to automate the creation of all that with Pulumi. I was initially drawn to create an automation API app in Typescript / Go but now wondering if environents and the cloud offering can take care of a customer-per-infrastructure thing without getting blown up or bogged down

If the infrastructure for each customer is essentially the same (or the differences can be easily parameterized), then using a single project with a separate stack per customer is probably the right approach. You could use a Pulumi ESC environment for each customer, and link to that environment from the stack configuration; this will centralize the configuration data and make it easier to manage.

Does that help?