Closed
Bug 1618898
Opened 5 years ago
Closed 4 years ago
Exceute all Poucave checks during deployment
Categories
(Cloud Services :: Server: Remote Settings, task, P2)
Cloud Services
Server: Remote Settings
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: leplatrem, Assigned: leplatrem)
Details
Now that we have the endpoints monitored by Pingdom, and that alerts are received, we don't want to be alerted for configuration/deployment failures.
For example, currently, if a Redash key is misconfigured, the deployment will still succeed. We don't make sure that the checks run without failure (does not mean they're green and return true), and that cause «interruption».
We should add a deployment step that executes all the checks before substituting the old instance by the new one.
Depends on https://github.com/mozilla-services/poucave/pull/366
Assignee | ||
Comment 1•5 years ago
|
||
As discussed yesterday, we should consider successful exit code 0 and 1, and stop deployment on exit code = 2.
Assignee | ||
Updated•4 years ago
|
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•