3.1.0

@headphonejames optimised to pull the Blackouts via the Alerta model, instead of DB query. See #21.
@deesel Added support for multitenant deployments. See #23.

3.0.0

Starting with version 3.0.0 onwards, the plugin will gather the list of Blackouts straight from the database (instead of using the API, as previously). This should normally improve reliability, but as there's no caching involved, every alert notification coming in (before being evaluated and correlated) will cause a DB query.

The configuration options for caching are therefore no longer required.

Additionally, you can now have regular expressions on the environment name (athough via the Alerta UI you are only able to select the environments that have produced alerts, you can use whatever environment name via the API).

v2.0.2

Update setup.py

v2.0.1

Merge pull request #13 from mirceaulinic/api-error

Catch whenever there's an issue retrieving the Blackouts

v2.0.0

We currently act on the every alert in the post_receive which
evaluates the alert after it has been correlated et al. While this is
an optimal approach from some perspectives, it introduces some confusion
and the alert risks to be thrown to other plugins before it's been acted
on (for example displayed in Slack).
To work around this unfortunate design choice, moving the code to be
executed in pre_receive; this has the major disadvantage that every
alert would request the Blackouts API endpoint - but caching the results
into a file would alleviate this.

v1.0.5

Fix #6: Don't override the alerts status to blackout when it's 'closed' #7

v1.0.4

Version 1.0.4

v1.0.3

Version 1.0.3

v1.0.2

Merge pull request #4 from mirceaulinic/rel-1.0.2

Version 1.0.2

v1.0.1

Merge pull request #2 from mirceaulinic/set-status

Set blackout status only when not already set