release-0.1.7

Patch release to fix bug where wrong update_type was being passed when incident severity was changed via Slack (#141)

v0.1.6

Small release to include the ability to pre-load and cache all of the external users from your slack workspace (#131)

v0.1.5

Another small release - I think we'll try and do these releases little and often. This one fixes a regression where the timeline API was returning metadata as a string rather than JSON object (#138), and thanks to @danpalmer we've formatted the project using black, and set up import sorting & linting on CI (#135 ) 🎉

Hotfix: 0.1.4

This fixes an issue with the previous release, where a new timeline event_type was added that was longer than the maximum for the event_type field :(

Response v0.1.3

There are a bunch of improvements in this release. You can now override built in incident commands (#105), docs are better, and we've been bringing the timeline up to scratch - it will now include messages you've pinned in Slack and updates to incident fields. This is still only exposed in the REST API, and we'll need to add this to the UI.

Includes:

• Load built in incident commands before the custom ones #105
• Add Slack helpers for getting user group details #121
• Expose timeline event ID in TimelineEvent endpoint #124
• Optimise Dockerfile in demo app #115
• Add instructions about creating the SLACK_CLIENT #126
• Create timeline events from Slack pins #128
• Improve Auth #129
• Add timeline events on incident updates #134

Response v0.1.2

We've been continuing to improve the REST API. The rationale for this is to allow people to build their own customised UIs - we'll be doing some work on the built in UI to bring it up to speed at some point.

This includes:

• Add /api/incidents//actions endpoint (#106)
• Rename /api/ExternalUser to /api/users and make read only #107
• Add /incidents/bymonth/2019/08 endpoint #104
• Build up a timeline of events for incident reports #108
• Periodically remind incident lead to close incident #109
• Fix string format - exceptions were not being logged #110
• Add "is_closed" field to /api/incidents #111
• Include Slack channel name in /api/incidents response #113
• Nudge incident lead to complete a report on close #112

Response v0.1.1 🎉

We've been working on a ton of improvements and new features for Response. Some of the highlights:

• We restructured Response to work as a standalone Django app you can import into your own Django projects
• Response is now published on PyPI
• We now have tests running on Travis CI (#59)
• We've done some internal refactoring - in particular, we've improved the way we handle errors from the Slack API, making debugging much easier (#83)
• We've started working on improving the REST API (#95)

This is quite a big change (for the better) in how Response can be integrated and deployed. Previously, Response was a standalone Django project in itself. This meant that users (including Monzo) had to keep a private fork up-to-date with upstream, pulling in changes and resolving merge conflicts 😞

Unfortunately we had to temporarily remove a few features, including:

• Escalation to Pagerduty
• Updating the statuspage
• Custom workflows

After consideration, we think we implemented these in the wrong way in the earlier editions - they were very hardcoded in and difficult to customise. Here's an issue tracking adding these back in: #125

This change vastly improves the workflow. You can now set up your own Django project (even using the tutorial), install Response from PyPI, and import it as a Django app. You'll then be able to customize Django to your needs (e.g. adding SSO/Oauth). Full instructions are in the README, and there's an example demo project which shows how to use Response.

Unfortunately

We'll be continuing to push out patch releases regularly - it's likely there will be breaking changes while we get settled on a stable API, but we'll do our best to keep you informed when these happen.

Above all, thanks to all our early users for their patience and feedback - please keep raising issues and PRs. We're really excited about where we can take this tool ❤️

First response release on PyPI!

We've been busy migrating Response to a standalone Django app published on PyPI to make it much easier to import and use in your own projects (#33). This is the inaugural edition of it on PyPI - we're still testing things and validating that everything's been moved over, so please raise an issue if you spot anything odd with this release 🎉

Tarball SHA: 37b28f31ff87757ce139be4e978ace58278364035aa2fe3a33707c6ebe480c18