Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs update for policy violation webhooks #13099

Merged
merged 4 commits into from
Oct 15, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions content/docs/pulumi-cloud/webhooks.md
Original file line number Diff line number Diff line change
Expand Up @@ -182,6 +182,8 @@ The following table describes the various event filters available and the contex
| `drift_detection_failed` | `drift_detection` | Organization or Stack | When a drift detection run fails. |
| `drift_remediation_succeeded` | `drift_remediation` | Organization or Stack | When a drift remediation run succeeds. |
| `drift_remediation_failed` | `drift_remediation` | Organization or Stack | When a drift remediation run fails. |
| `policy_violation_mandatory` | `policy_violation` | Organization or Stack | When a mandatory policy violation is detected. |
| `policy_violation_advisory` | `policy_violation` | Organization or Stack | When an advisory policy violation is detected. |

And this table describes the various filter groups available to easily subscribe to all events within a group.

Expand Down Expand Up @@ -233,8 +235,7 @@ to authenticate messages as coming from the Pulumi Cloud.
Each webhook payload has a format specific to the payload being emitted. Every payload will contain a sender, organization,
and stack reference as appropriate. For examples of specific payloads, see _Payload Reference_ below.

Each webhook will contain a `user` field, which is the user who requested the action, an `organization` which is
the organization name, and a URL for the event. It will also contain `projectName` and `stackName` when applicable.
Each webhook will contain an `organization` field, which is the organization name, and a URL for the event. It may also contain the `user` who requested the action, as well as the `projectName` and `stackName` when applicable.

##### Stack Creation

Expand Down
Loading