@faable/faable 1.38.0 → 1.38.1

package/dist/api/FaableApi.js

@@ -108,9 +108,6 @@ class FaableApi {
     async getApp(app_id) {
         return data(this.client.get(`/app/${app_id}`));
     }
-    async getRegistry(app_id) {
-        return data(this.client.get(`/app/${app_id}/registry`));
-    }
     // `image`/`type` are optional to support the failure path: a failed build
     // is recorded as a deployment without an image (and without `type`, which
     // would otherwise rewrite the app's runtime_strategy server-side).

package/dist/commands/deploy/inspect/detail.js

@@ -99,11 +99,10 @@ const deployment_detail = (args) => {
     if (artifact?.purged_at) {
         lines.push(label('Purged', `${when(artifact.purged_at)} — source no longer stored`));
     }
-    if (d.image)
-        lines.push(label('Image', d.image));
-    if (d.status?.runtime_image) {
-        lines.push(label('Runtime', d.status.runtime_image));
-    }
+    // Deliberately NOT rendered: `image` and `status.runtime_image`. Both are
+    // full registry references to OUR infrastructure (account, region, repo
+    // naming) — platform internals with no use to the app's owner. The runtime
+    // that matters is already on the Artifact line.
     if (d.redeploy_of)
         lines.push(label('Rebuild of', d.redeploy_of));
     if (d.quota_released_at) {

package/dist/log.js

@@ -8,11 +8,34 @@ import { buildLog } from './lib/log_buffer.js';
 //
 // Tee: terminal stream (colorized) + a plain-text copy into the build-log
 // buffer so CLI messages land in the logs attached to the deployment.
+// What the terminal shows: just the message. pino's envelope
+// (`[12:03:44.101] INFO (54834):`) is noise for a CLI — a timestamp and a pid
+// per line are for a log file, not for someone waiting on a deploy.
+//
+// Dropping the level token would also drop its color (pino-pretty tints the
+// whole line cyan otherwise), so the level is carried by the MESSAGE color
+// instead: warnings yellow, errors red, everything else the usual cyan.
+const LEVEL_COLOR = {
+    40: "\u001b[33m", // warn
+    50: "\u001b[31m", // error
+    60: "\u001b[31m", // fatal
+};
+const TERMINAL_FORMAT = {
+    ignore: "pid,hostname,time,level",
+    messageFormat: (log, key) => {
+        const message = String(log[key] ?? "");
+        const color = LEVEL_COLOR[Number(log.level)];
+        return color ? `${color}${message}\u001b[39m` : message;
+    },
+};
+// The archived copy KEEPS the envelope: these lines are attached to the
+// deployment and read later (support, post-mortems), where the timestamp and
+// level are the whole point.
 const toPlainText = prettyFactory({ colorize: false, sync: true });
 // NB: the two-arg form matters — pino(multistream) alone would treat the
 // multistream object as the options bag and log raw JSON to stdout.
 const log = pino({}, pino.multistream([
-    { stream: pretty({ colorize: true, sync: true }) },
+    { stream: pretty({ colorize: true, sync: true, ...TERMINAL_FORMAT }) },
     {
         stream: {
             write(line) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@faable/faable",
-  "version": "1.38.0",
+  "version": "1.38.1",
   "main": "dist/index.js",
   "license": "MIT",
   "author": "Marc Pomar <marc@faable.com>",