Skip to content

Add back Statuspage and PagerDuty integrations #125

@milesbxf

Description

@milesbxf

As in #116, we removed a few things from the 0.1.1 release (PagerDuty, Statuspage), as they didn't fit very well with the new code structure.

We also now think hardcoding them in is the wrong approach - it isn't really sustainable to have an optional settings section for each, when only a subset of users might use each bit.

Instead the new approach we're thinking of taking is creating a recipes directory, which would have subdirectories with Python files that people can simply drop into their own projects to use.

Alternatives we've considered:

Some kind of plugin system
Publishing integrations as separate importable Python/Django apps that people can install with pip

We think both of these are a bit too heavyweight - we'd like it to be as easy as possible both to create new integrations, and for people to install them. Both of these add friction to that, whereas copying + pasting some Python isn't too bad. We can reevaluate later on if this isn't the case.

It also prevents people from making their own customisations pretty easily.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions