Chronos Gateway 0.4.4
The plain-words diff of a run never shows a masked column's value; A deleted webhook gets nothing more; A webhook's URL is never logged, and its secret is kept sealed
- The plain-words diff of a run never shows a masked column's value. Its changes (an approval link, the console,
GET /v1/runs/:id/changes) read(masked)there, as the undo preview already did; the engine's admin diff shows them. - A deleted webhook gets nothing more. Deliveries still due to it were sent on through their retries, about 8.6 hours, approval links in Slack messages included; they are dropped now.
- A webhook's URL is never logged, and its secret is kept sealed. A Slack webhook's URL is its credential: the give-up warning names the webhook's id, and the error kept with a delivery leaves the URL out. Secrets made before are read as they are.
- One receiver that doesn't answer no longer holds the others back. A webhook or an effects channel whose receiver timed out (or refused the connection) is tried once a pass; its other deliveries wait for the next, so Slack approvals and refunds on other channels go out meanwhile.
- A Chronos Cloud undo of a run is recorded in the run, as through the API: the run says
undone,merge.undonegoes to the webhooks, and the run's merges are undone together (a part of them, 400). - MongoDB tools write all of a call's documents or none.
mongo_insertandmongo_update_manycheck every document before the first is written: a bad one refused the call after the ones before it were written, and a retry wrote those twice. - MongoDB updates work beside a masked ObjectId or integer field. A lifted field the update leaves alone is neither checked nor written; one the run read masked (as text) failed every update of the collection.
- A MongoDB tool call counts its writes against
GATEWAY_RUN_STATEMENTS_PER_MINUTE, before the first: one call counted once however many documents it wrote. A call with more writes than the limit left is refused whole (429). - A new setup code works after a lockout. The count of wrong setup codes is kept with the code, so one made by
chronos-gateway setup-code(another process) starts again, as the error says; before, only a restart did. deploy/compose.yamlpullslatestby default, not 0.2.11, whose image can't start its engine.- The run list, status counts and sweeper use indexes, and webhook deliveries done with for 30 days are deleted once an hour: each of these read every run, under the store's one lock, at every call.