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 back Statuspage and PagerDuty integrations #125

Open
milesbxf opened this issue Sep 4, 2019 · 4 comments
Open

Add back Statuspage and PagerDuty integrations #125

milesbxf opened this issue Sep 4, 2019 · 4 comments

Comments

@milesbxf
Copy link
Contributor

milesbxf commented Sep 4, 2019

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.

@AshleyPoole
Copy link
Contributor

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.

When you say this, for PagerDuty, StatusPage, etc, will those be shipped as packages? As the community and Monoz build more integrations, having them installed via Pip would allow us to version control them and more easily share them.

For unique handlers/actions/integrations relating to an individual company, having a recipes type approach would help for those "one off" type items.

@milesbxf
Copy link
Contributor Author

milesbxf commented Sep 5, 2019

When you say this, for PagerDuty, StatusPage, etc, will those be shipped as packages? As the community and Monoz build more integrations, having them installed via Pip would allow us to version control them and more easily share them.

Initially, no, though it'd be great to set up something like further down the line. I think it'd be good to start simple and see what works.

@ricardo-chaves-movile
Copy link

I'd love to test the Statuspage feature, any news of that?

@TomTucka
Copy link

@milesbxf Is there anything we can do to help get the PagderDuty integration added back in? We've decided to use Monzo Response as our incident tool and this feature is something we'd really like!

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

No branches or pull requests

4 participants