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 43ba511317..59d0fd5def 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 @@ -16,23 +16,23 @@ Notification configuration including: [Notification Route](../configuration-reference/#notificationroute) matches events based on their metadata like `name`, `group`, `app`, `labels`. Below is the list of supporting event names and their groups. -| Event | Group | Supported | -|-|-|-| -| DEPLOYMENT_TRIGGERED | DEPLOYMENT |

| -| DEPLOYMENT_PLANNED | DEPLOYMENT |

| -| DEPLOYMENT_APPROVED | DEPLOYMENT |

| -| DEPLOYMENT_WAIT_APPROVAL | DEPLOYMENT |

| -| DEPLOYMENT_ROLLING_BACK | DEPLOYMENT |

| -| DEPLOYMENT_SUCCEEDED | DEPLOYMENT |

| -| DEPLOYMENT_FAILED | DEPLOYMENT |

| -| DEPLOYMENT_CANCELLED | DEPLOYMENT |

| -| DEPLOYMENT_TRIGGER_FAILED | DEPLOYMENT |

| -| APPLICATION_SYNCED | APPLICATION_SYNC |

| -| APPLICATION_OUT_OF_SYNC | APPLICATION_SYNC |

| -| APPLICATION_HEALTHY | APPLICATION_HEALTH |

| -| APPLICATION_UNHEALTHY | APPLICATION_HEALTH |

| -| PIPED_STARTED | PIPED |

| -| PIPED_STOPPED | PIPED |

| +| Event | Group | Supported | Description | +|-|-|-|-| +| DEPLOYMENT_TRIGGERED | DEPLOYMENT |

| | +| DEPLOYMENT_PLANNED | 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) | +| DEPLOYMENT_SUCCEEDED | DEPLOYMENT |

| | +| DEPLOYMENT_FAILED | DEPLOYMENT |

| | +| DEPLOYMENT_CANCELLED | DEPLOYMENT |

| | +| DEPLOYMENT_TRIGGER_FAILED | DEPLOYMENT |

| | +| APPLICATION_SYNCED | APPLICATION_SYNC |

| | +| APPLICATION_OUT_OF_SYNC | APPLICATION_SYNC |

| | +| APPLICATION_HEALTHY | APPLICATION_HEALTH |

| | +| APPLICATION_UNHEALTHY | APPLICATION_HEALTH |

| | +| PIPED_STARTED | PIPED |

| | +| PIPED_STOPPED | PIPED |

| | ### Sending notifications to Slack diff --git a/docs/content/en/docs-v0.39.x/user-guide/managing-piped/configuring-notifications.md b/docs/content/en/docs-v0.39.x/user-guide/managing-piped/configuring-notifications.md index 32961eba9a..9a731981ed 100644 --- a/docs/content/en/docs-v0.39.x/user-guide/managing-piped/configuring-notifications.md +++ b/docs/content/en/docs-v0.39.x/user-guide/managing-piped/configuring-notifications.md @@ -16,23 +16,23 @@ Notification configuration including: [Notification Route](../configuration-reference/#notificationroute) matches events based on their metadata like `name`, `group`, `app`, `labels`. Below is the list of supporting event names and their groups. -| Event | Group | Supported | -|-|-|-| -| DEPLOYMENT_TRIGGERED | DEPLOYMENT |

| -| DEPLOYMENT_PLANNED | DEPLOYMENT |

| -| DEPLOYMENT_APPROVED | DEPLOYMENT |

| -| DEPLOYMENT_WAIT_APPROVAL | DEPLOYMENT |

| -| DEPLOYMENT_ROLLING_BACK | DEPLOYMENT |

| -| DEPLOYMENT_SUCCEEDED | DEPLOYMENT |

| -| DEPLOYMENT_FAILED | DEPLOYMENT |

| -| DEPLOYMENT_CANCELLED | DEPLOYMENT |

| -| DEPLOYMENT_TRIGGER_FAILED | DEPLOYMENT |

| -| APPLICATION_SYNCED | APPLICATION_SYNC |

| -| APPLICATION_OUT_OF_SYNC | APPLICATION_SYNC |

| -| APPLICATION_HEALTHY | APPLICATION_HEALTH |

| -| APPLICATION_UNHEALTHY | APPLICATION_HEALTH |

| -| PIPED_STARTED | PIPED |

| -| PIPED_STOPPED | PIPED |

| +| Event | Group | Supported | Description | +|-|-|-|-| +| DEPLOYMENT_TRIGGERED | DEPLOYMENT |

| | +| DEPLOYMENT_PLANNED | 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) | +| DEPLOYMENT_SUCCEEDED | DEPLOYMENT |

| | +| DEPLOYMENT_FAILED | DEPLOYMENT |

| | +| DEPLOYMENT_CANCELLED | DEPLOYMENT |

| | +| DEPLOYMENT_TRIGGER_FAILED | DEPLOYMENT |

| | +| APPLICATION_SYNCED | APPLICATION_SYNC |

| | +| APPLICATION_OUT_OF_SYNC | APPLICATION_SYNC |

| | +| APPLICATION_HEALTHY | APPLICATION_HEALTH |

| | +| APPLICATION_UNHEALTHY | APPLICATION_HEALTH |

| | +| PIPED_STARTED | PIPED |

| | +| PIPED_STOPPED | PIPED |

| | ### Sending notifications to Slack diff --git a/docs/content/en/docs-v0.40.x/user-guide/managing-piped/configuring-notifications.md b/docs/content/en/docs-v0.40.x/user-guide/managing-piped/configuring-notifications.md index 32961eba9a..9a731981ed 100644 --- a/docs/content/en/docs-v0.40.x/user-guide/managing-piped/configuring-notifications.md +++ b/docs/content/en/docs-v0.40.x/user-guide/managing-piped/configuring-notifications.md @@ -16,23 +16,23 @@ Notification configuration including: [Notification Route](../configuration-reference/#notificationroute) matches events based on their metadata like `name`, `group`, `app`, `labels`. Below is the list of supporting event names and their groups. -| Event | Group | Supported | -|-|-|-| -| DEPLOYMENT_TRIGGERED | DEPLOYMENT |

| -| DEPLOYMENT_PLANNED | DEPLOYMENT |

| -| DEPLOYMENT_APPROVED | DEPLOYMENT |

| -| DEPLOYMENT_WAIT_APPROVAL | DEPLOYMENT |

| -| DEPLOYMENT_ROLLING_BACK | DEPLOYMENT |

| -| DEPLOYMENT_SUCCEEDED | DEPLOYMENT |

| -| DEPLOYMENT_FAILED | DEPLOYMENT |

| -| DEPLOYMENT_CANCELLED | DEPLOYMENT |

| -| DEPLOYMENT_TRIGGER_FAILED | DEPLOYMENT |

| -| APPLICATION_SYNCED | APPLICATION_SYNC |

| -| APPLICATION_OUT_OF_SYNC | APPLICATION_SYNC |

| -| APPLICATION_HEALTHY | APPLICATION_HEALTH |

| -| APPLICATION_UNHEALTHY | APPLICATION_HEALTH |

| -| PIPED_STARTED | PIPED |

| -| PIPED_STOPPED | PIPED |

| +| Event | Group | Supported | Description | +|-|-|-|-| +| DEPLOYMENT_TRIGGERED | DEPLOYMENT |

| | +| DEPLOYMENT_PLANNED | 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) | +| DEPLOYMENT_SUCCEEDED | DEPLOYMENT |

| | +| DEPLOYMENT_FAILED | DEPLOYMENT |

| | +| DEPLOYMENT_CANCELLED | DEPLOYMENT |

| | +| DEPLOYMENT_TRIGGER_FAILED | DEPLOYMENT |

| | +| APPLICATION_SYNCED | APPLICATION_SYNC |

| | +| APPLICATION_OUT_OF_SYNC | APPLICATION_SYNC |

| | +| APPLICATION_HEALTHY | APPLICATION_HEALTH |

| | +| APPLICATION_UNHEALTHY | APPLICATION_HEALTH |

| | +| PIPED_STARTED | PIPED |

| | +| PIPED_STOPPED | PIPED |

| | ### Sending notifications to Slack diff --git a/docs/content/en/docs-v0.41.x/user-guide/managing-piped/configuring-notifications.md b/docs/content/en/docs-v0.41.x/user-guide/managing-piped/configuring-notifications.md index 32961eba9a..537f4b3c86 100644 --- a/docs/content/en/docs-v0.41.x/user-guide/managing-piped/configuring-notifications.md +++ b/docs/content/en/docs-v0.41.x/user-guide/managing-piped/configuring-notifications.md @@ -16,23 +16,23 @@ Notification configuration including: [Notification Route](../configuration-reference/#notificationroute) matches events based on their metadata like `name`, `group`, `app`, `labels`. Below is the list of supporting event names and their groups. -| Event | Group | Supported | -|-|-|-| -| DEPLOYMENT_TRIGGERED | DEPLOYMENT |

| -| DEPLOYMENT_PLANNED | DEPLOYMENT |

| -| DEPLOYMENT_APPROVED | DEPLOYMENT |

| -| DEPLOYMENT_WAIT_APPROVAL | DEPLOYMENT |

| -| DEPLOYMENT_ROLLING_BACK | DEPLOYMENT |

| -| DEPLOYMENT_SUCCEEDED | DEPLOYMENT |

| -| DEPLOYMENT_FAILED | DEPLOYMENT |

| -| DEPLOYMENT_CANCELLED | DEPLOYMENT |

| -| DEPLOYMENT_TRIGGER_FAILED | DEPLOYMENT |

| -| APPLICATION_SYNCED | APPLICATION_SYNC |

| -| APPLICATION_OUT_OF_SYNC | APPLICATION_SYNC |

| -| APPLICATION_HEALTHY | APPLICATION_HEALTH |

| -| APPLICATION_UNHEALTHY | APPLICATION_HEALTH |

| -| PIPED_STARTED | PIPED |

| -| PIPED_STOPPED | PIPED |

| +| Event | Group | Supported | Description | +|-|-|-|-| +| DEPLOYMENT_TRIGGERED | DEPLOYMENT |

| | +| DEPLOYMENT_PLANNED | DEPLOYMENT |

| | +| DEPLOYMENT_APPROVED | DEPLOYMENT |

| | +| DEPLOYMENT_WAIT_APPROVAL | DEPLOYMENT |

| | +| DEPLOYMENT_ROLLING_BACK | DEPLOYMENT |

| | +| DEPLOYMENT_SUCCEEDED | DEPLOYMENT |

| | +| DEPLOYMENT_FAILED | DEPLOYMENT |

| | +| DEPLOYMENT_CANCELLED | DEPLOYMENT |

| | +| DEPLOYMENT_TRIGGER_FAILED | DEPLOYMENT |

| | +| APPLICATION_SYNCED | APPLICATION_SYNC |

| | +| APPLICATION_OUT_OF_SYNC | APPLICATION_SYNC |

| | +| APPLICATION_HEALTHY | APPLICATION_HEALTH |

| | +| APPLICATION_UNHEALTHY | APPLICATION_HEALTH |

| | +| PIPED_STARTED | PIPED |

| | +| PIPED_STOPPED | PIPED |

| | ### Sending notifications to Slack diff --git a/docs/content/en/docs-v0.42.x/user-guide/managing-piped/configuring-notifications.md b/docs/content/en/docs-v0.42.x/user-guide/managing-piped/configuring-notifications.md index 32961eba9a..9a731981ed 100644 --- a/docs/content/en/docs-v0.42.x/user-guide/managing-piped/configuring-notifications.md +++ b/docs/content/en/docs-v0.42.x/user-guide/managing-piped/configuring-notifications.md @@ -16,23 +16,23 @@ Notification configuration including: [Notification Route](../configuration-reference/#notificationroute) matches events based on their metadata like `name`, `group`, `app`, `labels`. Below is the list of supporting event names and their groups. -| Event | Group | Supported | -|-|-|-| -| DEPLOYMENT_TRIGGERED | DEPLOYMENT |

| -| DEPLOYMENT_PLANNED | DEPLOYMENT |

| -| DEPLOYMENT_APPROVED | DEPLOYMENT |

| -| DEPLOYMENT_WAIT_APPROVAL | DEPLOYMENT |

| -| DEPLOYMENT_ROLLING_BACK | DEPLOYMENT |

| -| DEPLOYMENT_SUCCEEDED | DEPLOYMENT |

| -| DEPLOYMENT_FAILED | DEPLOYMENT |

| -| DEPLOYMENT_CANCELLED | DEPLOYMENT |

| -| DEPLOYMENT_TRIGGER_FAILED | DEPLOYMENT |

| -| APPLICATION_SYNCED | APPLICATION_SYNC |

| -| APPLICATION_OUT_OF_SYNC | APPLICATION_SYNC |

| -| APPLICATION_HEALTHY | APPLICATION_HEALTH |

| -| APPLICATION_UNHEALTHY | APPLICATION_HEALTH |

| -| PIPED_STARTED | PIPED |

| -| PIPED_STOPPED | PIPED |

| +| Event | Group | Supported | Description | +|-|-|-|-| +| DEPLOYMENT_TRIGGERED | DEPLOYMENT |

| | +| DEPLOYMENT_PLANNED | 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) | +| DEPLOYMENT_SUCCEEDED | DEPLOYMENT |

| | +| DEPLOYMENT_FAILED | DEPLOYMENT |

| | +| DEPLOYMENT_CANCELLED | DEPLOYMENT |

| | +| DEPLOYMENT_TRIGGER_FAILED | DEPLOYMENT |

| | +| APPLICATION_SYNCED | APPLICATION_SYNC |

| | +| APPLICATION_OUT_OF_SYNC | APPLICATION_SYNC |

| | +| APPLICATION_HEALTHY | APPLICATION_HEALTH |

| | +| APPLICATION_UNHEALTHY | APPLICATION_HEALTH |

| | +| PIPED_STARTED | PIPED |

| | +| PIPED_STOPPED | PIPED |

| | ### Sending notifications to Slack diff --git a/docs/content/en/docs-v0.43.x/user-guide/managing-piped/configuring-notifications.md b/docs/content/en/docs-v0.43.x/user-guide/managing-piped/configuring-notifications.md index 32961eba9a..537f4b3c86 100644 --- a/docs/content/en/docs-v0.43.x/user-guide/managing-piped/configuring-notifications.md +++ b/docs/content/en/docs-v0.43.x/user-guide/managing-piped/configuring-notifications.md @@ -16,23 +16,23 @@ Notification configuration including: [Notification Route](../configuration-reference/#notificationroute) matches events based on their metadata like `name`, `group`, `app`, `labels`. Below is the list of supporting event names and their groups. -| Event | Group | Supported | -|-|-|-| -| DEPLOYMENT_TRIGGERED | DEPLOYMENT |

| -| DEPLOYMENT_PLANNED | DEPLOYMENT |

| -| DEPLOYMENT_APPROVED | DEPLOYMENT |

| -| DEPLOYMENT_WAIT_APPROVAL | DEPLOYMENT |

| -| DEPLOYMENT_ROLLING_BACK | DEPLOYMENT |

| -| DEPLOYMENT_SUCCEEDED | DEPLOYMENT |

| -| DEPLOYMENT_FAILED | DEPLOYMENT |

| -| DEPLOYMENT_CANCELLED | DEPLOYMENT |

| -| DEPLOYMENT_TRIGGER_FAILED | DEPLOYMENT |

| -| APPLICATION_SYNCED | APPLICATION_SYNC |

| -| APPLICATION_OUT_OF_SYNC | APPLICATION_SYNC |

| -| APPLICATION_HEALTHY | APPLICATION_HEALTH |

| -| APPLICATION_UNHEALTHY | APPLICATION_HEALTH |

| -| PIPED_STARTED | PIPED |

| -| PIPED_STOPPED | PIPED |

| +| Event | Group | Supported | Description | +|-|-|-|-| +| DEPLOYMENT_TRIGGERED | DEPLOYMENT |

| | +| DEPLOYMENT_PLANNED | DEPLOYMENT |

| | +| DEPLOYMENT_APPROVED | DEPLOYMENT |

| | +| DEPLOYMENT_WAIT_APPROVAL | DEPLOYMENT |

| | +| DEPLOYMENT_ROLLING_BACK | DEPLOYMENT |

| | +| DEPLOYMENT_SUCCEEDED | DEPLOYMENT |

| | +| DEPLOYMENT_FAILED | DEPLOYMENT |

| | +| DEPLOYMENT_CANCELLED | DEPLOYMENT |

| | +| DEPLOYMENT_TRIGGER_FAILED | DEPLOYMENT |

| | +| APPLICATION_SYNCED | APPLICATION_SYNC |

| | +| APPLICATION_OUT_OF_SYNC | APPLICATION_SYNC |

| | +| APPLICATION_HEALTHY | APPLICATION_HEALTH |

| | +| APPLICATION_UNHEALTHY | APPLICATION_HEALTH |

| | +| PIPED_STARTED | PIPED |

| | +| PIPED_STOPPED | PIPED |

| | ### Sending notifications to Slack diff --git a/docs/content/en/docs-v0.44.x/user-guide/managing-piped/configuring-notifications.md b/docs/content/en/docs-v0.44.x/user-guide/managing-piped/configuring-notifications.md index e69af6d8bd..4991e199ab 100644 --- a/docs/content/en/docs-v0.44.x/user-guide/managing-piped/configuring-notifications.md +++ b/docs/content/en/docs-v0.44.x/user-guide/managing-piped/configuring-notifications.md @@ -16,23 +16,23 @@ Notification configuration including: [Notification Route](../configuration-reference/#notificationroute) matches events based on their metadata like `name`, `group`, `app`, `labels`. Below is the list of supporting event names and their groups. -| Event | Group | Supported | -|-|-|-| -| DEPLOYMENT_TRIGGERED | DEPLOYMENT |

| -| DEPLOYMENT_PLANNED | DEPLOYMENT |

| -| DEPLOYMENT_APPROVED | DEPLOYMENT |

| -| DEPLOYMENT_WAIT_APPROVAL | DEPLOYMENT |

| -| DEPLOYMENT_ROLLING_BACK | DEPLOYMENT |

| -| DEPLOYMENT_SUCCEEDED | DEPLOYMENT |

| -| DEPLOYMENT_FAILED | DEPLOYMENT |

| -| DEPLOYMENT_CANCELLED | DEPLOYMENT |

| -| DEPLOYMENT_TRIGGER_FAILED | DEPLOYMENT |

| -| APPLICATION_SYNCED | APPLICATION_SYNC |

| -| APPLICATION_OUT_OF_SYNC | APPLICATION_SYNC |

| -| APPLICATION_HEALTHY | APPLICATION_HEALTH |

| -| APPLICATION_UNHEALTHY | APPLICATION_HEALTH |

| -| PIPED_STARTED | PIPED |

| -| PIPED_STOPPED | PIPED |

| +| Event | Group | Supported | Description | +|-|-|-|-| +| DEPLOYMENT_TRIGGERED | DEPLOYMENT |

| | +| DEPLOYMENT_PLANNED | 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) | +| DEPLOYMENT_SUCCEEDED | DEPLOYMENT |

| | +| DEPLOYMENT_FAILED | DEPLOYMENT |

| | +| DEPLOYMENT_CANCELLED | DEPLOYMENT |

| | +| DEPLOYMENT_TRIGGER_FAILED | DEPLOYMENT |

| | +| APPLICATION_SYNCED | APPLICATION_SYNC |

| | +| APPLICATION_OUT_OF_SYNC | APPLICATION_SYNC |

| | +| APPLICATION_HEALTHY | APPLICATION_HEALTH |

| | +| APPLICATION_UNHEALTHY | APPLICATION_HEALTH |

| | +| PIPED_STARTED | PIPED |

| | +| PIPED_STOPPED | PIPED |

| | ### Sending notifications to Slack diff --git a/docs/content/en/docs-v0.45.x/user-guide/managing-piped/configuring-notifications.md b/docs/content/en/docs-v0.45.x/user-guide/managing-piped/configuring-notifications.md index 43ba511317..f7a4ed6934 100644 --- a/docs/content/en/docs-v0.45.x/user-guide/managing-piped/configuring-notifications.md +++ b/docs/content/en/docs-v0.45.x/user-guide/managing-piped/configuring-notifications.md @@ -16,23 +16,23 @@ Notification configuration including: [Notification Route](../configuration-reference/#notificationroute) matches events based on their metadata like `name`, `group`, `app`, `labels`. Below is the list of supporting event names and their groups. -| Event | Group | Supported | -|-|-|-| -| DEPLOYMENT_TRIGGERED | DEPLOYMENT |

| -| DEPLOYMENT_PLANNED | DEPLOYMENT |

| -| DEPLOYMENT_APPROVED | DEPLOYMENT |

| -| DEPLOYMENT_WAIT_APPROVAL | DEPLOYMENT |

| -| DEPLOYMENT_ROLLING_BACK | DEPLOYMENT |

| -| DEPLOYMENT_SUCCEEDED | DEPLOYMENT |

| -| DEPLOYMENT_FAILED | DEPLOYMENT |

| -| DEPLOYMENT_CANCELLED | DEPLOYMENT |

| -| DEPLOYMENT_TRIGGER_FAILED | DEPLOYMENT |

| -| APPLICATION_SYNCED | APPLICATION_SYNC |

| -| APPLICATION_OUT_OF_SYNC | APPLICATION_SYNC |

| -| APPLICATION_HEALTHY | APPLICATION_HEALTH |

| -| APPLICATION_UNHEALTHY | APPLICATION_HEALTH |

| -| PIPED_STARTED | PIPED |

| -| PIPED_STOPPED | PIPED |

| +| Event | Group | Supported | Description | +|-|-|-|-| +| DEPLOYMENT_TRIGGERED | DEPLOYMENT |

| | +| DEPLOYMENT_PLANNED | DEPLOYMENT |

| | +| DEPLOYMENT_APPROVED | DEPLOYMENT |

| | +| DEPLOYMENT_WAIT_APPROVAL | DEPLOYMENT |

| | +| DEPLOYMENT_ROLLING_BACK | DEPLOYMENT |

| | +| DEPLOYMENT_SUCCEEDED | DEPLOYMENT |

| | +| DEPLOYMENT_FAILED | DEPLOYMENT |

| | +| DEPLOYMENT_CANCELLED | DEPLOYMENT |

| | +| DEPLOYMENT_TRIGGER_FAILED | DEPLOYMENT |

| | +| APPLICATION_SYNCED | APPLICATION_SYNC |

| | +| APPLICATION_OUT_OF_SYNC | APPLICATION_SYNC |

| | +| APPLICATION_HEALTHY | APPLICATION_HEALTH |

| | +| APPLICATION_UNHEALTHY | APPLICATION_HEALTH |

| | +| PIPED_STARTED | PIPED |

| | +| PIPED_STOPPED | PIPED |

| | ### Sending notifications to Slack