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.

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

Integrate slack notifications into SDE curation workflow #677

Closed
9 tasks done
bishwaspraveen opened this issue Apr 22, 2024 · 2 comments · Fixed by #681
Closed
9 tasks done

Integrate slack notifications into SDE curation workflow #677

bishwaspraveen opened this issue Apr 22, 2024 · 2 comments · Fixed by #681
Assignees

Comments

@bishwaspraveen
Copy link
Contributor

bishwaspraveen commented Apr 22, 2024

Description

We need a way to communicate the life cycle of a collection in an automated way. Slack notifications is the solution we are considering for this implementation.

Notifications need to be sent the sde-internal channel on Slack when the workflow statuses of the collections change as shown below :

Workflow status changes that need to be captured

Preview Give feedback

Implementation

The message on slack should include the following details :

  • Tags that include people responsible for the next task on the source.
  • Name of the source which is a hyperlink to the collection detail page on the webapp.
  • A clear message that depicts the status of update.

Add the following slack webhook URL to the environment variable SLACK_WEBHOOK_URL during deployment: https://hooks.slack.com/services/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

Deliverable

Here are a few examples on how the slack notifications look like :
image
image

@code-geek
Copy link
Contributor

This is still in sprint 1 and open. Should we move it to sprint 2 or close it? Maybe close this one and create a follow up card about deploying to prod.

@bishwaspraveen
Copy link
Contributor Author

Yeah, I like the idea of creating a follow-up card. I'll do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants