@everystack/cli 0.4.7 → 0.4.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@everystack/cli",
-  "version": "0.4.7",
+  "version": "0.4.8",
   "description": "CLI and OTA updates for Expo apps on everystack",
   "license": "AGPL-3.0-only",
   "author": "Scalable Technology, Inc. <licensing@scalable.technology>",
@@ -82,7 +82,7 @@
     "structured-headers": "1.0.1",
     "tsx": "4.21.0",
     "typescript": "5.9.3",
-    "@everystack/model": "0.4.1"
+    "@everystack/model": "0.4.2"
   },
   "peerDependencies": {
     "@everystack/server": ">=0.1.0",

package/src/cli/commands/db-apply.ts

@@ -35,6 +35,7 @@ import { resolveDbSource, createUrlRunner, connectingVia, type DbSource } from '
 import { resolveConfig, opsFunction } from '../config.js';
 import { invokeAction, lambdaQueryRunner } from '../aws.js';
 import { executeApplyPlan, type ApplyPlanResult } from '../apply-execute.js';
+import { pgDumpPreflightError } from './db-backup.js';
 import { step, success, fail, info, warn } from '../output.js';
 
 // The apply core lives in apply-execute.ts (shared with the ops Lambda's
@@ -116,6 +117,19 @@ async function applyPlanViaStage(
 
   info(`plan ${planHash(plan).slice(0, 12)}: ${plan.fromFingerprint.slice(0, 12)} → ${plan.toFingerprint.slice(0, 12)} (${plan.executable} statement(s)${plan.destructive ? `, ${plan.destructive} destructive` : ''})`);
 
+  // A destructive staged apply snapshots via db:backup INSIDE the Lambda, before the DDL. Preflight
+  // that capability HERE so a missing/incompatible pg_dump layer fails fast with the install remedy —
+  // not deep in the ceremony after the authority check, the way it once surfaced mid-apply.
+  if (plan.destructive > 0) {
+    step('Preflighting the pg_dump layer (the destructive apply snapshots before the DDL)...');
+    const probe: any = await invokeAction(region, fn, 'db:backup:probe', {}).catch((err: any) => ({ error: err?.message ?? String(err) }));
+    const remedy = pgDumpPreflightError(probe);
+    if (remedy) {
+      fail(`Cannot take the pre-apply snapshot — the destructive plan was NOT applied.\n${remedy}`);
+      process.exit(1);
+    }
+  }
+
   try {
     // Descent — the fast-forward rule needs the git checkout, so the CLI
     // decides it (the Lambda has no checkout). Read the stage's state read-only

package/src/cli/commands/db-backup.ts

@@ -48,7 +48,7 @@ export async function dbBackupProbeCommand(flags: Record<string, string>): Promi
 
   if (result?.error) {
     fail(result.error);
-    info('Build + publish the layer with scripts/build-pgdump-layer.sh, export PGDUMP_LAYER_ARN, then redeploy.');
+    info('Install @everystack/pg-tools and redeploy — the layer attaches automatically. For a bring-your-own layer, pass pgDumpLayer(..., { layerArn }) in sst.config.ts.');
     process.exit(1);
   }
 
@@ -71,7 +71,7 @@ export async function dbBackupProbeCommand(flags: Record<string, string>): Promi
 export function pgDumpPreflightError(probe: any): string | null {
   if (!probe || probe.error) {
     const detail = probe?.error ?? 'the pg_dump layer probe returned no result';
-    return `${detail}\nBuild + publish the layer with scripts/build-pgdump-layer.sh, export PGDUMP_LAYER_ARN, then redeploy.`;
+    return `${detail}\nInstall @everystack/pg-tools and redeploy — the layer attaches automatically. For a bring-your-own layer, pass pgDumpLayer(..., { layerArn }) in sst.config.ts.`;
   }
   if (probe.compatible === false) {
     return `pg_dump ${probe.pgDump ?? '(unknown)'} (major ${probe.pgDumpMajor}) is older than the server (major ${probe.serverMajor}) — it will refuse to dump (no bypass exists). Rebuild the layer with pg_dump >= ${probe.serverMajor}.`;

package/src/cli/commands/deploy.ts

@@ -11,7 +11,7 @@
  */
 
 import { spawn } from 'node:child_process';
-import { step, success, fail, info } from '../output.js';
+import { step, success, fail, info, warn } from '../output.js';
 import { invalidateCachedConfig } from '../discover.js';
 import { resolveConfig } from '../config.js';
 import { probeDeployedFunctions } from '../deploy-probe.js';
@@ -23,11 +23,11 @@ export function buildDeployArgs(flags: Record<string, string>): string[] {
 }
 
 /**
- * The environment the sst child receives: the FULL ambient environment plus color.
- * Pinned as an explicit, tested contract because a consumer observed PGDUMP_LAYER_ARN
- * reaching sst when invoked directly but not through this wrapper — sst.config.ts
- * conditionals like `process.env.PGDUMP_LAYER_ARN ? { layers: [...] } : {}` silently
- * collapse when a variable goes missing, and the deploy still exits green.
+ * The environment the sst child receives: the FULL ambient environment plus color. The wrapper
+ * forwards everything so a consumer's own sst.config.ts env reads behave the same run directly or
+ * through `everystack deploy`. (This contract was pinned when the pg_dump layer depended on
+ * PGDUMP_LAYER_ARN reaching sst — now deprecated: the layer ships via @everystack/pg-tools +
+ * pgDumpLayer() and reads no ambient env at deploy.)
  */
 export function deployEnv(base: Record<string, string | undefined>): Record<string, string | undefined> {
   return { ...base, FORCE_COLOR: '1' };
@@ -38,11 +38,11 @@ export async function deployCommand(flags: Record<string, string>): Promise<void
   const args = buildDeployArgs(flags);
 
   step(`Deploying stage "${stage}"...`);
-  // Say what the wrapper sees: an sst.config.ts conditional on an env var collapses
-  // SILENTLY when the var is missing, and the deploy still exits green — the operator
-  // must be able to tell "the wrapper never saw it" from "sst ignored it" at a glance.
+  // PGDUMP_LAYER_ARN is deprecated: the layer now ships via @everystack/pg-tools and pgDumpLayer()
+  // needs no env var. Still forwarded to sst for one more minor (pgDumpLayer honors it as an alias),
+  // then removed — surface it loudly so the operator migrates off it.
   if (process.env.PGDUMP_LAYER_ARN) {
-    info(`pg_dump layer: PGDUMP_LAYER_ARN is set → forwarded to sst (${process.env.PGDUMP_LAYER_ARN})`);
+    warn('PGDUMP_LAYER_ARN is DEPRECATED and will be removed next minor. The pg_dump layer now ships via @everystack/pg-tools + pgDumpLayer() with no env var. Drop it once your sst.config.ts uses pgDumpLayer().');
   }
   await new Promise<void>((resolve) => {
     // `npx` resolves the consumer's local sst (the same way the export step runs expo).