From 98d56d2460aee34f426a2720db074ef5dae2e84c Mon Sep 17 00:00:00 2001 From: Dan Biwer Date: Thu, 10 Oct 2024 16:36:41 -0500 Subject: [PATCH 1/4] docs for policy violation webhooks --- content/docs/pulumi-cloud/webhooks.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/docs/pulumi-cloud/webhooks.md b/content/docs/pulumi-cloud/webhooks.md index 3b90d74e9f55..64e2c5a4d33a 100644 --- a/content/docs/pulumi-cloud/webhooks.md +++ b/content/docs/pulumi-cloud/webhooks.md @@ -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. From 6a9390f6ec94755d01421dacc225d4de32aa2849 Mon Sep 17 00:00:00 2001 From: Dan Biwer Date: Mon, 14 Oct 2024 18:00:09 -0500 Subject: [PATCH 2/4] not all webhooks require user --- content/docs/pulumi-cloud/webhooks.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/docs/pulumi-cloud/webhooks.md b/content/docs/pulumi-cloud/webhooks.md index 64e2c5a4d33a..80e03ef60e17 100644 --- a/content/docs/pulumi-cloud/webhooks.md +++ b/content/docs/pulumi-cloud/webhooks.md @@ -235,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 will also contain the `user` who requested the action, `projectName` and `stackName` when applicable. ##### Stack Creation From ee1fdc6bc6fb124885e86d7c85b02cab4cd9ea97 Mon Sep 17 00:00:00 2001 From: Dan Biwer Date: Mon, 14 Oct 2024 18:07:21 -0500 Subject: [PATCH 3/4] words --- content/docs/pulumi-cloud/webhooks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/pulumi-cloud/webhooks.md b/content/docs/pulumi-cloud/webhooks.md index 80e03ef60e17..83608da1c0e8 100644 --- a/content/docs/pulumi-cloud/webhooks.md +++ b/content/docs/pulumi-cloud/webhooks.md @@ -235,7 +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 an `organization` field, which is the organization name, and a URL for the event. It will also contain the `user` who requested the action, `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, `projectName`, and `stackName` when applicable. ##### Stack Creation From e6801c1c83a6f7586d95518d10b8b7c2ed483e85 Mon Sep 17 00:00:00 2001 From: Dan Biwer Date: Mon, 14 Oct 2024 18:11:58 -0500 Subject: [PATCH 4/4] words --- content/docs/pulumi-cloud/webhooks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/pulumi-cloud/webhooks.md b/content/docs/pulumi-cloud/webhooks.md index 83608da1c0e8..89f41dde86f2 100644 --- a/content/docs/pulumi-cloud/webhooks.md +++ b/content/docs/pulumi-cloud/webhooks.md @@ -235,7 +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 an `organization` field, which is the organization name, and a URL for the event. It may also contain the `user` who requested the action, `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