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

Add AlertSourceType model #58

Closed
ddabble opened this issue Jun 18, 2020 · 0 comments · Fixed by #61
Closed

Add AlertSourceType model #58

ddabble opened this issue Jun 18, 2020 · 0 comments · Fixed by #61
Assignees
Labels

Comments

@ddabble
Copy link
Contributor

ddabble commented Jun 18, 2020

AlertSource.type is currently a "choice field" with hardcoded choices. We should convert this into a foreign key to a new model - AlertSourceType, which enables users to register their own alert source types. This should be done in conjunction with adding glue services for incoming alerts (see #44), instead of having code in the backend for every alert source type, as is currently facilitated for (see mapping.py).

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

Successfully merging a pull request may close this issue.

2 participants