Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added Sample to Slack Notify Step #9406

Closed
wants to merge 1 commit into from
Closed

Added Sample to Slack Notify Step #9406

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions docs/continuous-delivery/deploy-srv-diff-platforms/aws/asg-tutorial.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1347,16 +1347,20 @@ Harness stores configurations of the ASG you are deploying twice:
</Tabs4>


### 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:[email protected]) to enable this feature.
Currently, ASG Steady State Step is behind the feature flag `CDS_ASG_SKIP_INSTANCE_TERMINATION`. Please contact [Harness support](mailto:[email protected]) to enable this feature.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Currently, ASG Steady State Step is behind the feature flag `CDS_ASG_SKIP_INSTANCE_TERMINATION`. Please contact [Harness support](mailto:[email protected]) to enable this feature.
Currently, the ASG Steady State Step is behind the feature flag `CDS_ASG_SKIP_INSTANCE_TERMINATION`. Please contact [Harness support](mailto:[email protected]) 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.
Expand Down
10 changes: 8 additions & 2 deletions ...tinuous-delivery/x-platform-cd-features/cd-steps/utilities/slack-notify-step.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ Follow the steps below to set up a Slack notify step:
</TabItem>
</Tabs>

:::note
:::info
The Slack Notify step **can be added in any stage**, but it is **only available within a step group**.
:::

Expand Down Expand Up @@ -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)
![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.