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

they are basically entirely separate jobs

Everyone does this stuff differently, and being able to use a programming language certainly makes it easier to apply this kind of environment/stack-specific logic. But the best practice is probably to use configuration to capture the differences between environments, and use a single program to cover all of them. (So not much logical difference between them.)

for now i've just taken the tack that if code belongs in one environment, but not another, it's a different project. so here i just created a new "project" for the pipeline itself

i was really... really not into introspecting the environment to execute conditional resources (if it wasn't a multiplier or something reasonable)