Skip to main content

IaC Code Generalization Layer

Feature Requests

Add a wrapper layer or templating system to generalize hardcoded infrastructure.
We are building a DR site. Legacy infra uses hardcoded AZs, regions, IPs. We want a way to override those values at run-time without rewriting all the stacks.

  • Support for param overrides by env/org/region

  • Higher-level orchestration abstraction

  • Impact: Easier DR rollout, improves code reuse and hygiene

Status: 🗑️ Archived2 comments

Log in to comment and vote

Comments2

  • Natalia Gazda

    Team•

    Jul 16

    Hey, thanks for the suggestion. We're archiving this one for now. It hasn't picked up much interest since it went up, so it isn't on our near-term roadmap. Archiving isn't deleting: the request stays on record, and if it gathers more votes or comments we can bring it back. If it still matters to you, add a vote or a comment so we can gauge the demand.

  • Natalia Gazda

    Team•

    Jul 24, 2025

    @Koby Yakov thanks for submitting this. I’m not exactly sure I understand what do you mean by that request, could you please provide a bit more context?

    When you mention "support for param overrides by env/org/region", could you help us unpack that a bit?

    • Are you referring to environment variables, stack inputs, Terraform variables… or something else?

    • Are you working with a single stack that targets multiple environments, or multiple stacks with shared code?

    • What’s hard or risky about the current setup?

    • What would a “good” solution look like to you?

    Appreciate any context you can share — the more we understand the job you’re trying to do, the better we can shape the right path forward.