Skip to main content

stack dependency references should be able to use nested outputs

Feature RequestsStack Dependencies

We would like to use nested output values (e.g. reference a key in an output map) for stack dependency refs. Currently there is no way to reference a nested output value as a stack dependency reference. This is a limitation because we can’t dynamically generate outputs to help stacks determine when to run and not.

Workaround
Problem
Status: 🗑️ Archived1 comment

Log in to comment and vote

Comments1

  • Black Breeze

    •

    May 8, 2025

    Hey — thanks for flagging this. I want to make sure we really understand what you’re trying to accomplish here, because right now I’m a bit unclear on the setup and constraints.

    You mentioned generating stacks dynamically via “customer specs” (not Terraform)—can you walk me through what that means in practice? For example:

    • What creates the Stack? Is this through our API or some custom automation?

    • What’s the shape of a “customer spec”? Is that a JSON config, a form in your app, something else?

    • What’s the role of nested outputs in that process—are you trying to drive when another stack runs, or something else?

    If you’ve got a real-world example, that’d be super helpful. Just want to make sure we’re solving the right problem before we jump to implementation.