basrieter / service.addondata.sync / issues / #5 - implement a kill switch in case a version goes bad — Bitbucket

Issue #5 closed

Bas Rieter repo owner created an issue 2017-08-28

If, for some reason, there is a very bad bug introduced, we don't want syncs to proceed until a new version is installed.

Perhaps we can use a TXT DNS record to specify broken versions? So they won't sync anymore?

Comments (3)

Bas Rieter reporter
- changed title to implement a kill switch in case a version goes bad
- 2017-08-28T22:26:19+00:00
Bas Rieter reporter
- changed status to resolved
Added: DNS kill-switch to stop syncing in case of problems (Fixes #5)

→ <<cset 0d24046f4d1b>>
- 2017-09-01T23:14:18+00:00
Bas Rieter reporter
- changed status to closed
- 2017-09-18T07:11:55+00:00
Log in to comment

Assignee: –

Type: bug

Priority: major

Status: closed

Votes: 0

Watchers: 1

Jira: the preferred issue tracker for Bitbucket. Join the team!