From 075d84e6d9f94997b2b662f4f819f05922cb43e3 Mon Sep 17 00:00:00 2001 From: Colin Saliceti Date: Tue, 29 Aug 2023 18:00:37 +0100 Subject: [PATCH] WIP --- source/infrastructure/monitoring/slack/index.html.md.erb | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/infrastructure/monitoring/slack/index.html.md.erb b/source/infrastructure/monitoring/slack/index.html.md.erb index 36bbb3e8..6cda88a8 100644 --- a/source/infrastructure/monitoring/slack/index.html.md.erb +++ b/source/infrastructure/monitoring/slack/index.html.md.erb @@ -54,3 +54,9 @@ Test manually using the `curl` command shown on the "Incoming webhooks" page - Ideally store the webhook as a [secret in keyvault](/infrastructure/security/managing-secrets/). - Retrieve the secret with [the az cli action](https://github.com/marketplace/actions/azure-cli-action) - Use a Github actions like [action-slack-notify](https://github.com/rtCamp/action-slack-notify) to post the message to the channel + +## Recover app +If all the app collaborators have left, the webhooks can't be updated. It is required to recover the app to add a collaborator. +- Use an existing Slack notification from this app. Find the app URL from the +- Go to the #requests-slack channel +- Choose a workflow and request to be added as a collaborator on the app