Chronos/DBWaitlist

Changelog / Chronos Gateway

Chronos Gateway 0.3.2

Undo after a partial undo; Undo after a part was approved

With Chronos DB 0.5.27 changesDownloads

  • Undo after a partial undo. A partly_undone run can be undone again: rows the first undo put back aren't counted as changed, and once the rows left hold what the run wrote, they go back and the run becomes undone. The console's button reads "Undo the rest". With an engine before 0.5.2 the second undo needs skip_changed.
  • Undo after a part was approved. A held run with a part approved (only_tables, only_keys) and the rest rejected, expired or discarded kept the part's rows in the database with no way to undo them through the gateway. POST /v1/runs/:id/undo and the console's Undo take such a run now.
  • PUT /v1/policy answers ended: the rules that were set and the new set left out. The API doc's example sent a part of the rules, which ends max_deletes = 0; it sends them all now and says so.
  • A Slack message is made once per delivery: a retry sends the same approval or undo link instead of making a new one each time (while the gateway runs; a restart makes one more).
  • Slack messages name MariaDB as MariaDB, not MySQL.
  • mongo_update_many and mongo_delete_many say in their descriptions that a filter matching more than 1,000 documents is refused, not cut to the first 1,000.
  • Docs: a write Postgres refuses under act_as fails the run (run.failed), not merge.rejected; approved_by.by from a developer key is the caller's word, unchecked.
Chronos Gateway 0.3.2 · Chronos