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.)
m
mammoth-art-6111
02/14/2022, 8:58 PM
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
👍 1
mammoth-art-6111
02/14/2022, 8:59 PM
i was really... really not into introspecting the environment to execute conditional resources (if it wasn't a multiplier or something reasonable)