@madewithremy/admin 0.1.46 → 0.1.47

package/dist/prod.js

@@ -2138,6 +2138,29 @@ function query2(ctx, sql) {
     { queries: [{ sql }] }
   );
 }
+function history(ctx, params = {}) {
+  return call(
+    ctx,
+    "GET",
+    `/_internal/v2/apps/${ctx.appId}/db/history${qs({ limit: params.limit, cursor: params.cursor })}`
+  );
+}
+function historyQuery(ctx, releaseId, sql) {
+  return call(
+    ctx,
+    "POST",
+    `/_internal/v2/apps/${ctx.appId}/db/history/query`,
+    { releaseId, queries: [{ sql }] }
+  );
+}
+function historyAttach(ctx, releaseId, sql) {
+  return call(
+    ctx,
+    "POST",
+    `/_internal/v2/apps/${ctx.appId}/db/history/attach`,
+    { releaseId, queries: [{ sql }] }
+  );
+}
 
 // src/commands/db.ts
 var dbSpecs = {
@@ -2150,11 +2173,46 @@ var dbSpecs = {
   },
   "db tables": {
     usage: "Usage: remy-admin db tables"
+  },
+  "db history": {
+    usage: "Usage: remy-admin db history [--limit 20] [--cursor <nextCursor>]",
+    flags: {
+      limit: { type: "number", min: 1, max: 100 },
+      cursor: { type: "string" }
+    }
+  },
+  // raw, as `db query` is: the SQL is taken verbatim.
+  "db history query": {
+    usage: "Usage: remy-admin db history query <releaseId> <sql>",
+    raw: true,
+    positionals: [
+      { name: "releaseId", required: true },
+      { name: "sql", required: true }
+    ]
+  },
+  "db history attach": {
+    usage: "Usage: remy-admin db history attach <releaseId> <sql>",
+    raw: true,
+    positionals: [
+      { name: "releaseId", required: true },
+      { name: "sql", required: true }
+    ]
   }
 };
 async function dbQuery(ctx, a) {
   out(await query2(ctx, a.req("sql")));
 }
+async function dbHistory(ctx, a) {
+  out(
+    await history(ctx, { limit: a.num("limit"), cursor: a.str("cursor") })
+  );
+}
+async function dbHistoryQuery(ctx, a) {
+  out(await historyQuery(ctx, a.req("releaseId"), a.req("sql")));
+}
+async function dbHistoryAttach(ctx, a) {
+  out(await historyAttach(ctx, a.req("releaseId"), a.req("sql")));
+}
 async function dbTables(ctx) {
   out(
     await query2(
@@ -2165,28 +2223,91 @@ async function dbTables(ctx) {
 }
 var dbHandlers = {
   "db query": dbQuery,
-  "db tables": dbTables
+  "db tables": dbTables,
+  "db history": dbHistory,
+  "db history query": dbHistoryQuery,
+  "db history attach": dbHistoryAttach
 };
-var dbHelp = `remy-admin db \u2014 Query the production database.
+var dbHelp = `remy-admin db \u2014 Query the production database, and the copies of it past releases kept.
 
 Subcommands:
-  query    Execute a SQL query against the live release's database
-  tables   List all tables in the database
+  query            Execute a SQL query against the live release's database
+  tables           List all tables in the database
+  history          List past releases' databases, newest first, with when each was live
+  history query    Read a past release's database (read-only)
+  history attach   Run SQL against live with a past release's database attached as "history"
 
 Usage:
   remy-admin db <sql>
   remy-admin db query <sql>
   remy-admin db tables
+  remy-admin db history [--limit 20] [--cursor <nextCursor>]
+  remy-admin db history query <releaseId> <sql>
+  remy-admin db history attach <releaseId> <sql>
+
+Past releases:
+  Every deploy copies the live database into the new release and keeps the
+  release it replaces, database and all, exactly as it stood at that moment.
+  So each entry 'db history' lists holds live as of its liveUntil: anything
+  written after that is only in later copies and in live, and nothing that
+  happened between two deploys is kept anywhere. The release live now is
+  listed first (current: true); its database is live, so use 'db query'.
+
+  'db history query' reads one of those copies, and nothing can change it: a
+  write is refused. Its schema is that release's, which may differ from
+  live's: SELECT name FROM sqlite_master lists its tables, and
+  PRAGMA table_info(<table>) a table's columns.
+
+  'db history attach' runs against live with the copy attached as the schema
+  "history": history.<table> is the past table, and an unqualified name is
+  live's. Writes to live are real, exactly as with 'db query', and a
+  statement runs as one transaction. The attached copy is private to the
+  call, so writing into it changes nothing anywhere.
+  PRAGMA history.table_info(<table>) shows a past table's columns.
+
+  Recovering data is a merge, not a rollback. Live has moved on since the
+  copy was made (rows added, edits people meant to make), so decide what
+  comes back: which rows, which columns, and what happens to anything
+  written since.
+  - Find the copy that has what's missing: the windows say where to look,
+    and a count or a few rows confirm it.
+  - Compare it with live through attach (a join on id, a count of what
+    differs) before changing anything.
+  - Write the repair to restore exactly that. Columns emptied in live,
+    filled back by id, leaving rows created since alone:
+      UPDATE orders SET note = h.note, total = h.total
+      FROM history.orders h
+      WHERE h.id = orders.id AND orders.note IS NULL
+    Rows deleted from live, put back:
+      INSERT INTO orders (id, note, total)
+      SELECT id, note, total FROM history.orders
+      WHERE id NOT IN (SELECT id FROM orders)
+  - Tell the user what will change and get their go-ahead before writing
+    live, as with any change to production.
+  If no copy covers the moment that matters, say so plainly rather than
+  restoring from the nearest one.
+
+Notes:
+  - SQL is taken verbatim: 'db query' and the two history commands that take
+    SQL don't parse flags, so a statement may safely begin with a '--'
+    comment. Always quote the SQL.
+  - The history commands use the database named as live's default.
+  - The first history command on a copy fetches it, so it takes longer for a
+    large database; the ones after it are quick.
+  - Errors: release_not_found (no release of this app that was ever live has
+    that id), release_is_live (it's the live release: use 'db query'),
+    no_database (that release has no database of live's name), sql_error
+    (the database refused the statement, a write to a past copy included;
+    nothing in it was applied).
 
 Examples:
   remy-admin db tables
   remy-admin db "SELECT * FROM users LIMIT 10"
   remy-admin db "INSERT INTO categories (name) VALUES ('Electronics')"
   remy-admin db query "SELECT * FROM users LIMIT 10"
-
-Notes:
-  - SQL is taken verbatim: this is the one command that does not parse flags, so
-    a statement may safely begin with a '--' comment. Always quote the SQL.`;
+  remy-admin db history --limit 5
+  remy-admin db history query <releaseId> "SELECT count(*) AS n FROM orders"
+  remy-admin db history attach <releaseId> "SELECT count(*) AS emptied FROM orders o JOIN history.orders h ON h.id = o.id WHERE o.note IS NULL AND h.note IS NOT NULL"`;
 
 // src/ops/secrets.ts
 function list6(ctx) {
@@ -3544,8 +3665,9 @@ Notes:
     of the store that holds objects; in a store holding both, a key is found
     wherever it is, and ls asks which.
   - Handing someone a large or sensitive file? Use a PRIVATE store + \`sign\`:
-    the link is unguessable, expires (--ttl seconds, max 7 days), and the object
-    stays deletable with \`rm\`. Never use the account media CDN
+    the link is unguessable, expires (--ttl seconds, max 7 days, or 3 hours
+    where it's a storage presign; expiresAt says which), and the object stays
+    deletable with \`rm\`. Never use the account media CDN
     (\`mindstudio upload\`) for sensitive material \u2014 those URLs are public and
     permanent.
   - put: the key defaults to a content hash (sha256) of the bytes, so
@@ -9819,7 +9941,7 @@ Commands:
   diagnostics   View the post-deploy Lighthouse audit (scores, issues, raw report)
   domains       Subdomain, custom domains, and buying a domain
   users         Manage app users and roles
-  db            Query the production database
+  db            Query the production database, and past releases' copies of it
   secrets       Manage app secrets (env vars)
   methods       List and invoke methods
   data          Sync databases between dev and live (lift-from-dev / lift-from-live)
@@ -9943,6 +10065,15 @@ ${guide}`;
   }
   return void 0;
 }
+function dbWordsEnd(argv) {
+  if (argv[1] === "query") {
+    return 3;
+  }
+  if (argv[1] === "history") {
+    return argv[2] === "query" || argv[2] === "attach" ? 4 : 3;
+  }
+  return 2;
+}
 function resolveHelp(argv) {
   const group = argv[0];
   if (!group || group === "--help" || group === "-h") {
@@ -9955,7 +10086,7 @@ function resolveHelp(argv) {
   if (argv.length === 1) {
     return groupHelp;
   }
-  const scan = group === "db" ? argv.slice(1, argv[1] === "query" ? 3 : 2) : argv.slice(1);
+  const scan = group === "db" ? argv.slice(1, dbWordsEnd(argv)) : argv.slice(1);
   if (!scan.some((t) => t === "--help" || t === "-h")) {
     return void 0;
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@madewithremy/admin",
-  "version": "0.1.46",
+  "version": "0.1.47",
   "description": "Admin SDK + CLI for managing production Remy apps",
   "type": "module",
   "main": "./dist/index.js",