Plan policy: an `info` rule that renders on the run without affecting autodeploy
Add an info (or note) rule to plan policies: a list of strings rendered in the run's Messages list the way warn is, in blue or green, with no effect on the run's outcome and no effect on autodeploy.
WorkaroundEmit `warn`, and keep autodeploy off on every stack the policy is attached to. That makes the summary and unattended applies mutually exclusive, and the run banner now reads WARN on an ordinary create — so WARN no longer signals that something is being destroyed.
ProblemA plan policy cannot show a reviewer anything without also deciding something.
The run renders only three rules:
- deny — fails the run.
- warn — marks the run for human review on an autodeploy stack.
- flag — decides nothing, but renders as a chip truncated from the right.
Our message
"module.platform[0].module.service[0].aws_cloudwatch_log_subscription_filter.service_tasks[0] would be created"
renders as
"module.platform[0].module.service[0].a…" — it names nothing.
A notification policy's `inbox` takes free text, but NotificationType has no RUN member, so the message attaches to a stack and never reaches the run; RunPolicyReceipt carries only flags, outcome and policy name, with no body.
So a policy that summarises a plan — so reviewers don't scroll pages of plan logs — has no surface to render on.