Skip to main content

Notification Policies Access to Variables

Feature Requests

We use stack contexts and environment variables to store useful metadata, such as the version being deployed.

However, notification policies do not have access to those context variables. Because of this, we have to run custom scripts before the plan step to expose values as flags, just so notifications can read them.

It would be much cleaner if notification policies had access to the same variables that plan policies do, including context-attached environment variables.

This would remove the need for workarounds and simplify our notification logic.

Status: ⬆️ Gathering votes1 comment

Log in to comment and vote

Comments1

  • Black Breeze

    •

    Mar 17

    Thanks for raising this @Rob Put . Can you please walk me through your release logic and how these variables are required for making policy decisions? It’s an unusual request in that in most cases folks appreciate the separation of concerns between runtime and policy input.

    Is it perhaps possible that you may be using notification policies where a simple POST request from a hook would be a simpler fit?