Chronos/DBWaitlist

Changelog / Chronos Gateway

Chronos Gateway 0.3.1

GATEWAY_FOLLOW beside MongoDB; MongoDB filters: $regex and dates; Undo from Slack

With Chronos DB 0.5.17 changesDownloads

  • GATEWAY_FOLLOW beside MongoDB (engine 0.5.1 or later): main takes MongoDB's changes about a second after they commit, through a change stream on each attached collection. The role the connection check gives has changeStream on those collections for it. With several databases, --follow is given only to engines of databases that are followed (not MySQL or MariaDB yet).
  • MongoDB filters: $regex and dates. The MongoDB tools (find, count, update_*, delete_*) take {"$regex": ..., "$options": "i"} on strings and arrays of strings, and compare dates ({"$date": ...}) with $eq $ne $gt $gte $lt $lte $in $nin as the instants they are. Both were refused by name before.
  • Undo from Slack. A Slack webhook's message of a merge carries a link, Review and undo: a page that shows what would go back and undoes that merge, once, until GATEWAY_APPROVAL_TTL (GATEWAY_SLACK_UNDO=off: no link; with single sign-on, a link to the run in the console). The undo is the checked one: rows changed since stay. Slack messages name the database they are about (MySQL, MongoDB), and say when a merge is undone.
  • Disconnect a database. DELETE /v1/sources/:name (and Disconnect on the console's Connect page) takes away a database connected under a name: its engine stops, the gateway's copy and settings of it go, its runs stay as history, and the database itself is left as it is. Runs still in progress there are refused (409 runs_live) or discarded with it (?discard_runs=true). A run that is over still reads after its database is disconnected.
  • Undo with the gateway's own role. The statements the connection check gives for the gateway's role (role_sql) now make and grant the table that keeps what merges write (chronos.merge_rows; chronos_merge_rows beside MySQL and MariaDB). A role made from the 0.3.0 statements or earlier has none, so undo wasn't ready there (merges were never affected). POST /v1/runs/:id/undo now answers 409 undo_not_ready with the statements to run once, in place of the database's own error; GET /v1/status says attached.undo.ready.
  • Several gateways starting at the same moment on an empty Postgres store (pods of one set) could fail once making its tables, and restart. They take turns now.
  • Console: pages name the database being looked at (MySQL, MongoDB) where they said Postgres; a conflict beside MySQL or MongoDB shows its rows to settle, as beside Postgres; a question left open (approve a delete) closes when you go to another page, where it could be answered about the wrong thing; undo on a database not set up for it shows the statements to run. The connection check beside MySQL no longer lists chronos_merge_rows as a table to attach.
Chronos Gateway 0.3.1 · Chronos