Chronos Gateway 0.3.2
Undo after a partial undo; Undo after a part was approved
- Undo after a partial undo. A
partly_undonerun 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 becomesundone. The console's button reads "Undo the rest". With an engine before 0.5.2 the second undo needsskip_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/undoand the console's Undo take such a run now. PUT /v1/policyanswersended: the rules that were set and the new set left out. The API doc's example sent a part of the rules, which endsmax_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_manyandmongo_delete_manysay 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_asfails the run (run.failed), notmerge.rejected;approved_by.byfrom a developer key is the caller's word, unchecked.