You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix obsolete navigation paths in ESC webhooks documentation (#16392)
Updates navigation instructions to reflect current Pulumi Cloud UI, where organization webhooks are now found under Integrations > Webhooks rather than Settings > Webhooks. Also reorders sections to present environment webhooks before organization webhooks for better logical flow.
Additional cleanup includes removing outdated trial callout and screenshot, fixing Python code example syntax errors, correcting grammar errors, and standardizing list formatting per style guide.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <[email protected]>
* Add admin permission requirement and fix navigation path for organization webhooks
Addresses PR feedback by documenting that organization webhook creation requires admin permissions and correcting the navigation path to Settings > Integrations > Webhooks.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <[email protected]>
---------
Co-authored-by: Claude <[email protected]>
Copy file name to clipboardExpand all lines: content/docs/esc/environments/webhooks.md
+40-46Lines changed: 40 additions & 46 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,69 +13,63 @@ aliases:
13
13
- /docs/esc/webhooks/
14
14
---
15
15
16
-
{{% notes "info" %}}
17
-
ESC Webhooks is a feature available on the Pulumi Team, Enterprise and Business Critical editions.
18
-
To try it out, start a [trial](https://app.pulumi.com/site/trial) now.
19
-
{{% /notes %}}
20
-
21
16
ESC Webhooks allow you to notify external services of events
22
17
happening within your ESC environments. For example,
23
18
you can trigger a notification whenever a new revision of an environment is created.
24
19
When an event occurs, Pulumi will notify the registered webhook listeners via a HTTP `POST`
25
20
request with metadata about the event. The webhook can then be used to emit a
26
21
notification, start running integration tests, or even update Pulumi stacks.
27
22
28
-
There are large number of real life applications for webhooks including serving as the foundation
29
-
of most _ChatOps_ workflows.
30
-
31
23
## Overview
32
24
33
-
ESC Webhooks can be attached to either an environment or an organization. Environment webhooks
34
-
will be notified of events specific to the environment. Organization
35
-
webhooks will be notified for events happening within each of the organization's
36
-
environments.
37
-
38
-
Organization webhooks can be managed on the Organization Settings page. Environment webhooks can be managed from the webhooks tab on each Environment's detail page.
25
+
ESC Webhooks can be attached to either an environment or a Pulumi Cloud organization:
-**Environment webhooks** will fire in response to events you specify for a single ESC environment.
28
+
-**Organization webhooks** can be configured to trigger in response to events you specify for _all_ environments in your Pulumi Cloud organization, in addition to other organization-wide events.
41
29
30
+
{{% notes "info" %}}
42
31
Pulumi Cloud also supports webhooks for events related to Pulumi IaC stacks and [Pulumi Deployments](/docs/pulumi-cloud/deployments). For additional information on these types of webhooks, see [Pulumi Cloud Webhooks](/docs/deployments/webhooks).
32
+
{{% /notes %}}
43
33
44
34
{{% notes "info" %}}
45
-
Webhooks do not guarantee event order. You should not assume events will be received in the order they occurred.
35
+
Webhooks do not guarantee ordered delivery of events. That is, you should not assume events will be received in the order in which they occurred.
46
36
{{% /notes %}}
47
37
48
38
### Create a Webhook
49
39
50
40
Pulumi Webhooks may be created through any of the following methods:
51
41
52
42
1. Manually, in the Pulumi Cloud UI using the steps outlined in [Create an Organization Webhook in the Pulumi Cloud UI](#create-an-organization-webhook-in-the-pulumi-cloud-ui) or [Create an Environment Webhook in Pulumi Cloud in the Pulumi Cloud UI](#create-an-environment-webhook-in-the-pulumi-cloud-ui).
53
-
1. Declaratively, as part of a [Pulumi IaC](/docs/iac) program as shown in [Create an Webhook in a Pulumi IaC Program](#create-an-webhook-in-a-pulumi-iac-program)
54
-
1. By invoking the [Pulumi Cloud REST API](/docs/pulumi-cloud/cloud-rest-api/#create-webhook) directly.
55
-
56
-
#### Create an Organization Webhook in the Pulumi Cloud UI
57
-
58
-
1. Navigate to **Settings** > **Webhooks**.
59
-
2. Select **Create webhook**.
60
-
3. Under Destination, choose **Webhook**, **Slack** or **Microsoft Teams**.
61
-
1. For generic JSON webhooks, provide a display name, payload URL, and optionally a secret.
62
-
2. For Slack webhooks, provide a Slack webhook URL and a display name.
63
-
3. For Microsoft Teams webhooks, provide a Microsoft Teams webhook URL and a display name.
64
-
4. Choose which events you would like to receive using groups and filters menu.
43
+
1. Declaratively, as part of a [Pulumi IaC](/docs/iac) program as shown in [Create a Webhook in a Pulumi IaC Program](#create-a-webhook-in-a-pulumi-iac-program)
44
+
1. By invoking the [Pulumi Cloud REST API](/docs/reference/cloud-rest-api/webhooks/#create-webhook) directly.
65
45
66
46
#### Create an Environment Webhook in the Pulumi Cloud UI
67
47
68
-
1. Navigate to your environment.
69
-
2. Navigate to **Webhooks** tab.
70
-
3. Select **Create webhook**.
71
-
4. Under Destination, choose **Webhook**, **Slack**, **Microsoft Teams** or **Deployment**
48
+
1. Navigate to the environment you wish to create a webhook for.
49
+
1. Navigate to **Webhooks** tab.
50
+
1. Select **Create webhook**.
51
+
1. Under Destination, choose **Webhook**, **Slack**, **Microsoft Teams** or **Deployment**
72
52
1. For generic JSON webhooks, provide a display name, payload URL, and optionally a secret.
73
-
2. For Slack webhooks, provide a Slack webhook URL and a display name.
74
-
3. For Microsoft Teams webhooks, provide a Microsoft Teams webhook URL and a display name.
75
-
4. For Deployment webhooks, provide the stack to deploy in the format `project/stack`.
76
-
5. Choose which events you would like to receive using groups and filters menu.
53
+
1. For Slack webhooks, provide a Slack webhook URL and a display name.
54
+
1. For Microsoft Teams webhooks, provide a Microsoft Teams webhook URL and a display name.
55
+
1. For Deployment webhooks, provide the stack to deploy in the format `project/stack`.
56
+
1. Choose which events you would like to receive using groups and filters menu.
57
+
58
+
#### Create an Organization Webhook in the Pulumi Cloud UI
77
59
78
-
#### Create an Webhook in a Pulumi IaC Program
60
+
{{% notes "info" %}}
61
+
You must be an admin of the organization to create organization webhooks.
1. Under Destination, choose **Webhook**, **Slack** or **Microsoft Teams**.
67
+
1. For generic JSON webhooks, provide a display name, payload URL, and optionally a secret.
68
+
1. For Slack webhooks, provide a Slack webhook URL and a display name.
69
+
1. For Microsoft Teams webhooks, provide a Microsoft Teams webhook URL and a display name.
70
+
1. Choose which events you would like to receive using groups and filters menu.
71
+
72
+
#### Create a Webhook in a Pulumi IaC Program
79
73
80
74
The following example shows how to create an Environment webhook in a Pulumi IaC program by declaring a [Webhook resource](/registry/packages/pulumiservice/api-docs/webhook/) with the [Pulumi Cloud provider](/registry/packages/pulumiservice).
81
75
@@ -101,13 +95,13 @@ const webhook = new pulumiservice.Webhook("example-webhook", {
0 commit comments