Skip to content
This repository has been archived by the owner on Jan 27, 2022. It is now read-only.

Be more defensive when reading statuspage incidents #5

Open
sciurus opened this issue Jul 26, 2018 · 1 comment
Open

Be more defensive when reading statuspage incidents #5

sciurus opened this issue Jul 26, 2018 · 1 comment

Comments

@sciurus
Copy link
Contributor

sciurus commented Jul 26, 2018

This tool is designed to

  1. Never open more than one statuspage incident for a component
  2. Never declare a statuspage incident as affecting more or less than one component

However, it should handle things properly if those conditions are violated. I think that means

  1. Close the fist incident and log an error for each additional incident
  2. Skip processing that incident, just as if it didn't have a component tag
@sciurus
Copy link
Contributor Author

sciurus commented Dec 13, 2018

Note that in #19 I'm considering how to relax the constraint "Never declare a statuspage incident as affecting more or less than one component"

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

No branches or pull requests

1 participant