Skip to content

Comments

Add Discord backend support to MessagingServiceConfig and related tests#265

Closed
neverabsolute wants to merge 5 commits intobugsink:mainfrom
neverabsolute:main
Closed

Add Discord backend support to MessagingServiceConfig and related tests#265
neverabsolute wants to merge 5 commits intobugsink:mainfrom
neverabsolute:main

Conversation

@neverabsolute
Copy link
Contributor

This pull request adds support for Discord as a messaging backend for alerts, alongside the existing Slack integration.

  • Added a new DiscordBackend implementation in alerts/service_backends/discord.py, including configuration form, test message and alert sending logic, and error/success status handling.
  • Updated the MessagingServiceConfig model in alerts/models.py to support a kind of "discord" and route backend selection based on this field.
  • Created a Django migration to add "discord" as a valid choice for the kind field.
  • Added tests for Discord backend error handling and status tracking in alerts/tests.py, I just copied the existing Slack ones.
image

@CLAassistant
Copy link

CLAassistant commented Nov 7, 2025

CLA assistant check
All committers have signed the CLA.

@neverabsolute
Copy link
Contributor Author

Without this piece in the Dockerfile, forks won't build from it. I'll erase this if and when it is ready to merge.

ARG VERSION
ENV SETUPTOOLS_SCM_PRETEND_VERSION_FOR_BUGSINK=${VERSION}

@vanschelven
Copy link
Contributor

This implements #121

@vanschelven
Copy link
Contributor

I'll take a look at this ASAP; I'll probably just "hijack" the PR to integrate it into main simultaneously with similar work on a mattermost-specific backend (#253)

@vanschelven
Copy link
Contributor

Without this piece in the Dockerfile, forks won't build from it.

Would be interested what in particular doesn't build

@vanschelven
Copy link
Contributor

Hijacked/continued here: #279

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 this pull request may close these issues.

3 participants