From 8ef2e30e997340f9a5735ea8f2b100d6c4148876 Mon Sep 17 00:00:00 2001 From: vishal-av Date: Thu, 13 Feb 2025 12:54:53 +0530 Subject: [PATCH] Added Sample to Slack Notify Step --- .../deploy-srv-diff-platforms/aws/asg-tutorial.md | 8 ++++++-- .../cd-steps/utilities/slack-notify-step.md | 10 ++++++++-- 2 files changed, 14 insertions(+), 4 deletions(-) diff --git a/docs/continuous-delivery/deploy-srv-diff-platforms/aws/asg-tutorial.md b/docs/continuous-delivery/deploy-srv-diff-platforms/aws/asg-tutorial.md index bf23f74a176..507171c628f 100644 --- a/docs/continuous-delivery/deploy-srv-diff-platforms/aws/asg-tutorial.md +++ b/docs/continuous-delivery/deploy-srv-diff-platforms/aws/asg-tutorial.md @@ -1347,16 +1347,20 @@ Harness stores configurations of the ASG you are deploying twice: -### Steady State Step +### ASG Steady State Step :::note -Currently, Asg Steady State Step is behind the feature flag `CDS_ASG_SKIP_INSTANCE_TERMINATION`. Please contact [Harness support](mailto:support@harness.io) to enable this feature. +Currently, ASG Steady State Step is behind the feature flag `CDS_ASG_SKIP_INSTANCE_TERMINATION`. Please contact [Harness support](mailto:support@harness.io) to enable this feature. ::: The **ASG Steady State Step** is an additional pipeline step designed to monitor the progress and completion of the Instance Refresh process in AWS Auto Scaling Groups (ASGs). It is introduced to ensure that, during an ASG rolling deployment, the deployment workflow proceeds as soon as the new instances are launched and have reached a healthy state. +:::warning +The ASG Steady State Step can only be added if the ASG Rolling Deploy Step is part of the stage or pipeline. It will **fail** if added alongside an ASG Blue-Green or Canary Deploy Step. +::: + **Key Features** - **Polls Instance Refresh Status**: Uses the DescribeInstanceRefreshes API to monitor the PercentageComplete and Status of the instance refresh. diff --git a/docs/continuous-delivery/x-platform-cd-features/cd-steps/utilities/slack-notify-step.md b/docs/continuous-delivery/x-platform-cd-features/cd-steps/utilities/slack-notify-step.md index da077521a28..3129b9d7243 100644 --- a/docs/continuous-delivery/x-platform-cd-features/cd-steps/utilities/slack-notify-step.md +++ b/docs/continuous-delivery/x-platform-cd-features/cd-steps/utilities/slack-notify-step.md @@ -74,7 +74,7 @@ Follow the steps below to set up a Slack notify step: -:::note +:::info The Slack Notify step **can be added in any stage**, but it is **only available within a step group**. ::: @@ -149,4 +149,10 @@ stages: Upon a successful pipeline run, the message you configured in the Slack Notify step will be sent to the designated Slack channel or recipient. -![Execution](./static/slack-notify.png) \ No newline at end of file +![Execution](./static/slack-notify.png) + +## Slack Notify Step Sample + +To see an example of how to setup a Slack Notify Step using Harness, visit the [Harness Community Repository](https://github.com/harness-community/harnesscd-example-apps/tree/master/cd-features/slack-notify-step). + +This repository provides a ready-to-use sample application and the necessary configuration files to help you get started quickly.