> If you feel the need to put code in your runtime config, that means your design sucks. I would look at Terraform and beg to differ - they started with a simp

> If you feel the need to put code in your runtime config, that means your design sucks. I would look at Terraform and beg to differ - they started with a simple stringly typed language and had to build a typed language. Still no support for conditionals, so everyone has to abuse the only bit of control flow on offer - ternary variables and counts. CircleCI is just as bad - it's a nice yaml format until you want a conditional step in workflow that's conditional on something other than the branch name. It's very risky to settle on a static config at design time since the users will find a need. How would you cater to that user without offering a programming interface to configure it?