[semver:major] Upgrade Slack to notify on failed deploys #23
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
With the current configuration, we only get Slack notifications about successful deployments, despite having the notification steps in the compiled CircleCI steps. This is an attempt to enable notifications for all cases. As part of this upgrade, Slack configuration needs to change. - **old** `SLACK_WEBHOOK_URL` - **new** `SLACK_ACCESS_TOKEN` through `moj-slack-notifications` context Slack orb 4+ requires an application to be set up and a `SLACK_ACCESS_TOKEN` variable. To enable this, we've installed an app called `ci-deploy-to-cloud-platform` on the MoJ Slack instance. The token is shared in the `moj-slack-notifications` CircleCI context. Please see [the example notification workflow][ex] for a usage example. [ex]: src/examples/slack_notification.yml
mikehalmamoj
approved these changes
Dec 18, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the current configuration, we only get Slack notifications about
successful deployments, despite having the notification steps in the
compiled CircleCI steps.
This is an attempt to enable notifications for all cases.
As part of this upgrade, Slack configuration needs to change.
SLACK_WEBHOOK_URLSLACK_ACCESS_TOKENthroughmoj-slack-notificationscontextSlack orb 4+ requires an application to be set up and a
SLACK_ACCESS_TOKENvariable. To enable this, we've installed an appcalled
ci-deploy-to-cloud-platformon the MoJ Slack instance.The token is shared in the
moj-slack-notificationsCircleCI context.Please see the example notification workflow for a usage example.