From 3330cb5e50f83b03a1617441a46f3489ffd00e9a Mon Sep 17 00:00:00 2001 From: Shinnosuke Sawada-Dazai Date: Fri, 15 Nov 2024 09:17:47 +0900 Subject: [PATCH] Add DEPLOYMENT_STARTED event to notifications documentation Signed-off-by: Shinnosuke Sawada-Dazai --- .../user-guide/managing-piped/configuring-notifications.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/content/en/docs-dev/user-guide/managing-piped/configuring-notifications.md b/docs/content/en/docs-dev/user-guide/managing-piped/configuring-notifications.md index 9e0c366108..4d45719d15 100644 --- a/docs/content/en/docs-dev/user-guide/managing-piped/configuring-notifications.md +++ b/docs/content/en/docs-dev/user-guide/managing-piped/configuring-notifications.md @@ -20,6 +20,7 @@ Below is the list of supporting event names and their groups. |-|-|-|-| | DEPLOYMENT_TRIGGERED | DEPLOYMENT |

| | | DEPLOYMENT_PLANNED | DEPLOYMENT |

| | +| DEPLOYMENT_STARTED | DEPLOYMENT |

| | | DEPLOYMENT_APPROVED | DEPLOYMENT |

| | | DEPLOYMENT_WAIT_APPROVAL | DEPLOYMENT |

| | | DEPLOYMENT_ROLLING_BACK | DEPLOYMENT |

| PipeCD sends a notification when a deployment is completed, while it does not send a notification when a deployment status changes to DEPLOYMENT_ROLLING_BACK because it is not a completion status. See [#4547](https://github.com/pipe-cd/pipecd/issues/4547) |