Skip to main content

informational rules in plan policies.

Feature RequestsBlueprintsUI/UXIntegrationsPoliciesStacksDashboardNotifications

Rules are currently evaluated on warn or deny, however in some scenarios its nice to give the user informational messages.
Specifically thinking of the Self-Service approach through blueprints, this is really handy for our users who aren’t familiar with IaC and code, however as it skips the PR element the benefits of infracost are somewhat diluted.
It would be great to have an informational rule that runs each time to provide the end user the updated cost of the resources deployed by the stack. I’m sure there will be other scenarios where an informational update in the stack would be useful.

Workaround
Status: ❌ Rejected2 comments

Log in to comment and vote

Comments2

  • Aleksandra Cieslak

    Team•

    Sep 7

    Thanks for the suggestion, and sorry for the long silence.

    After discussion, we're closing this one.

    For surfacing cost updates to end users, we think notification policies / enhanced policy outputs are the better fit, they let you route the signal somewhere it's guaranteed to land, rather than hoping it's noticed inline.

    The warn workaround remains the best option for now.

    Happy to revisit if concrete scenarios pile up, feel free to open a new request then.

  • Black Breeze

    •

    May 10, 2025

    Thanks for the suggestion.

    Right now, warn rules in plan policies always require human review on tracked runs. That’s intentional—it ensures the warning is seen and acted on. Introducing info rules would create a new category of policy signal that doesn’t block, warn, or notify. That raises a hard question:

    If there’s no guarantee the rule will be noticed—what role is it playing?

    We’re cautious about introducing behaviorless policy types. They tend to look like coverage without offering much control or visibility. If the goal is to surface something for awareness, we wonder whether that’s better handled through notification policies or enhanced policy outputs—where the signal can be routed intentionally.

    We’re open to digging deeper. Curious how you’d want these informational rules to show up—or be consumed—so they don’t just vanish into the noise.