@orchestraworks/worker 0.0.137 → 0.0.139

package/docs/REFERENCE.md

@@ -204,7 +204,7 @@ set is a concern this machine does not have.
 | `SFDK_EGRESS_LISTEN_PORT` | where the redirect lands, which is the shim's own listen port |
 | `SFDK_EGRESS_IPV6` | `true` mirrors the redirect through `ip6tables` |
 | `SFDK_EGRESS_PROXY` | `on`, the default, or `off`; `off` tells each harness that no edge of ours stands in front of this machine, as on an enrolled one. The platform writes `off` into every Launcher machine's boot file, because no proxy entrance of ours stands in front of one yet |
-| `SFDK_RUNTIME_ENVIRONMENT` | a whole environment folded into one JSON object of string values, for a boot file whose lines cannot carry a line break; each pair is placed unless already set |
+| `SFDK_RUNTIME_ENVIRONMENT` | a whole environment folded into one JSON object of string values, for a boot file whose lines cannot carry a line break; each pair is placed unless already set, except that with `SFDK_EGRESS_PROXY=off` a pair replaces a name that holds exactly the image's egress placeholder |
 | `SFDK_VOLUME_MOUNTS` | the volumes this launch declares, as one JSON document |
 | `SFDK_MACHINE_SLUG` | the machine's platform-minted slug: the leading label of its preview hostnames, and what the tunnel's upgrade signs |
 | `SFDK_TUNNEL_ENDPOINT_URL` | where the preview gateway serves its tunnel listener; its scheme is the whole TLS statement for that hop |
@@ -213,7 +213,11 @@ set is a concern this machine does not have.
 
 **The worker reads that file itself, on every operating system, and no service manager is handed it.**
 Every `worker run` places each pair into its own environment before it serves, leaving alone any name
-that is already set, so a person's own foreground run still wins over the file. systemd's
+that is already set, so a person's own foreground run still wins over the file. One name already set
+is replaced: where the switch `SFDK_EGRESS_PROXY` is `off`, no edge replaces the image's placeholder
+credential on the way out, so a value the launch declared replaces a name that holds exactly a
+placeholder the family facts list. That is how a customer's own token in `provisionSpec.env` reaches the
+harness on a Launcher machine; it rides the machine's startup data in plain text. systemd's
 `EnvironmentFile=` is deliberately not used: it processes backslash escapes in an unquoted value, so
 the two characters `\n` that carry a line break inside `SFDK_RUNTIME_ENVIRONMENT` would arrive as a bare
 `n` and the certificate folded in there would hold no certificate at all. A machine with no file

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@orchestraworks/worker",
-  "version": "0.0.137",
+  "version": "0.0.139",
   "type": "module",
   "description": "The Orchestra worker.",
   "license": "Apache-2.0",
@@ -22,10 +22,10 @@
     "docs/REFERENCE.md"
   ],
   "optionalDependencies": {
-    "@orchestraworks/worker-linux-x64": "0.0.137",
-    "@orchestraworks/worker-linux-arm64": "0.0.137",
-    "@orchestraworks/worker-darwin-x64": "0.0.137",
-    "@orchestraworks/worker-darwin-arm64": "0.0.137",
-    "@orchestraworks/worker-win32-x64": "0.0.137"
+    "@orchestraworks/worker-linux-x64": "0.0.139",
+    "@orchestraworks/worker-linux-arm64": "0.0.139",
+    "@orchestraworks/worker-darwin-x64": "0.0.139",
+    "@orchestraworks/worker-darwin-arm64": "0.0.139",
+    "@orchestraworks/worker-win32-x64": "0.0.139"
   }
 }