Skip to main content

Include the run_id of an upstream stack, and any other metadata in policy inputs.

Feature RequestsNotificationsStack DependenciesPoliciesSpacesStacks

We currently have a stack that when triggered triggers it’s dependencies. We want to create one notification policy and have a unique id that we can use for the entire dependency chain since run.id is per stack.

I tried to have the upstream’s stacks run_id as an output, but when dependent stacks get triggered the policies do not contain this information, nor the run_id of the upstream stack.

For our purposes just a triggered_by_run_id would be perfect, but in general the feature is to include all possible metadata. Especially on the inputs the stack received from the output of an upstream stack. Something like inputs.triggered_by_outputs would be nice too.

Workaround
Problem
Status: ✅ Completed4 comments

Log in to comment and vote

Comments4

  • Coral Chipmunk

    •

    Mar 18

    Yeah I would find that very helpful.

  • Purple Coast

    •

    Feb 18

    Maybe an array called dependency_metadata in a format like:

    [ {  "run_id": "...",  "depth": 0,  "outputs": []
 },
  {
   "run_id": "...",
   "depth:" 1,
   "outputs": []
   }
]

    Would handle all cases (depth 0 would be root, and so forth)

  • Coral Chipmunk

    •

    Feb 18

    If there are multiple levels of dependencies it would also be nice to track the run.id that originated all the runs.

  • Black Breeze

    •

    Feb 18

    Thanks for raising this @Peter Rakhunov. The request makes perfect sense and I can see how policies could benefit from being aware of the execution graph.

    I’m raising this directly with the dev team for further discovery and technical feasibility study. On the surface it looks reasonably simple but at the same time I don’t know what I don’t know.