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

That's what the stack files are for, usually. The configuration in (for example) Pulumi.dev.yaml would be different to the configuration in Pulumi.prod-apac.yaml and Pulumi.prod-emea.yaml... or whatever suits your environments.

For "parameters from outside", you can look up external resources (files, vaults, environment variables, etc.) in the normal way. You can key those things by stack name, or get values from vaults specific to each environment (maybe even deployed by other projects with the same stack names) or whatever suits your needs

I think the recent-ish addition of variables to `Pulumi.yaml` makes this a little less painful and repetitious though, right?

Well, your question seems to be about variables which would have different values for different stacks, so that would necessarily rule out project-wide values. But for variables that are project-wide, Pulumi.yaml does make things DRYer, yes.

So what about variables with different values for different stacks?

Yes. That's what Pulumi configuration is for.