@adonis-agora/durable 1.0.0-rc.15 → 1.0.0-rc.17

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @adonis-agora/durable
 
+## 1.0.0-rc.17
+
+### Major Changes
+
+- [#519](https://github.com/DavideCarvalho/adonis-agora-durable/pull/519) [`b0675e5`](https://github.com/DavideCarvalho/adonis-agora-durable/commit/b0675e5ed48a9e2e61b7c3e404539829363ec8b4) Thanks [@DavideCarvalho](https://github.com/DavideCarvalho)! - The console's list routes speak the `@adonis-agora/filter` wire format. `GET /api/runs`, `GET /api/runs/:id/fans/:group` and `GET /api/schedules` take filters in `filter[...]` (a filter field sent bare is a `400`, as are unknown fields and operators), `sort` checked against an allow-list (`-createdAt` only on runs, `seq` only on fan members; `key`, `workflow`, `nextFireAt`, `lastFireAt` on schedules), and `page` / `size`, and answer `{ data, meta: { total, perPage, currentPage, lastPage, firstPage } }`. `GET /api/runs` keeps `statuses` next to them and now reports the total (`countRuns`, or a full listing on a port without one). Fan members page by `page` / `size` instead of `offset` / `limit` and filter with `filter[status]=failed` instead of `failed=true`. Schedules gain `filter[workflow]`, `filter[namespace]`, `filter[paused]`. The scope of `POST /api/bulk/:action` and `GET /api/runs/values` is `filter[...]` too (values keeps `groupByCount[limit]` / `[offset]`). `GET /api/workers` answers `{ data }` instead of the bare array, `GET /api/health` `{ data }` instead of `{ groups }`. The console uses `@adonis-agora/filter-client` 1.0 rc. The dev tools `durable_list_fan_members` and `durable_list_schedules` page with `page` / `limit`. Requires `@adonis-agora/filter` 1.0.0-rc.5 or newer. The OpenAPI document declares the new parameters and envelopes.
+
+## 1.0.0-rc.16
+
+### Minor Changes
+
+- [#512](https://github.com/DavideCarvalho/adonis-agora-durable/pull/512) [`a3e57aa`](https://github.com/DavideCarvalho/adonis-agora-durable/commit/a3e57aa056a4ed202178e9a0154815c2ff4be87b) Thanks [@DavideCarvalho](https://github.com/DavideCarvalho)! - New `schema` option: the durable tables can live in a database schema of their own (a database on MySQL) while the app's connection keeps its default. Set it once at the top level of `config/durable.ts` (`schema: 'durable'`) for every durable table, or per piece with `stores.lucid({ schema })`, `transports.db({ schema })` and the queue transport's `workerKeysSchema`. Every statement the store, the db transport and the worker-key table issue names the schema, on any connection, the app's own transaction included; nothing changes the connection's `search_path` (which leaks behind PgBouncer in transaction mode). Boot creates the schema when it creates the tables, catalog lookups, the schema-heal lock and index checks are scoped to it, and SQLite with a `schema` fails at boot. `createDurableTables`, `dropDurableTables`, `createDurableTransportTables` and `dropDurableTransportTables` take `{ schema }`, the published migrations carry a `schema` constant, and `agora:doctor --deep` gains a `durable.schema` check. Without `schema`, nothing changes.
+
 ## 1.0.0-rc.15
 
 ### Patch Changes