@webpieces/cloudtasks-client 0.3.380 → 0.3.382

package/README.md

@@ -22,10 +22,11 @@ await scheduler.addToQueue(() => emailTasks.sendEmail(req), { dedupName: req.id
 - `ClientCloudTasksFactory.createPubSubClient(Api, TaskClientConfig)` — builds the enqueue proxy. It
   injects a `Provider<TaskProxyClient>` and calls `get()` per contract; `TaskProxyClient` is bound
   TRANSIENT, so each client gets its own. The delivery URL is resolved at enqueue time from `svcName`
-  via `resolveServiceUrl`: a `ClientRegistry` override wins, else on GCP it is derived from the Cloud
-  Run service name (same project + region, so you maintain no URL table), else (off-GCP, unregistered)
-  it throws. Register non-derivable URLs (localhost, cross-region, non-Cloud-Run) once at startup with
-  `ClientRegistry.addMapping(svcName, port)` / `addUrlMapping(svcName, url)`
+  through `ClientRegistry.resolve` — the SAME chain the RPC client runs: a registered mapping wins,
+  else the installed deriver (`ClientRegistry.setDeriver(gcpCloudRunDeriver())` on GCP), else it
+  throws, because an unresolvable target is a setup bug. Register non-derivable URLs (localhost,
+  cross-region, non-Cloud-Run) once at startup with `ClientRegistry.addMapping(svcName, port)` /
+  `addUrlMapping(svcName, url)`
 - An enqueue outside `RequestContext.run(...)` **throws**: a task with no caller trace is a bug
 - `CloudTaskScheduler` — `addToQueue` / `schedule` / `cancelJob`; carries scheduling
   options out-of-band so the contract signature stays identical on both sides

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@webpieces/cloudtasks-client",
-  "version": "0.3.380",
+  "version": "0.3.382",
   "description": "Cloud Tasks enqueue client generated from a shared @PubSub API contract (twin of http-client)",
   "type": "commonjs",
   "main": "./src/index.js",
@@ -23,9 +23,9 @@
     "access": "public"
   },
   "dependencies": {
-    "@webpieces/core-context": "0.3.380",
-    "@webpieces/core-util": "0.3.380",
-    "@webpieces/gcp-identity": "0.3.380",
+    "@webpieces/core-context": "0.3.382",
+    "@webpieces/core-util": "0.3.382",
+    "@webpieces/gcp-identity": "0.3.382",
     "@google-cloud/tasks": "5.5.2",
     "inversify": "7.10.4",
     "reflect-metadata": "0.2.2"

package/src/TaskClientConfig.d.ts

@@ -25,6 +25,12 @@ export declare class TaskClientConfig {
      * host — is a `ClientRegistry` mapping registered at startup, NOT a per-client URL.
      */
     svcName: string);
-    /** Resolved per enqueue, not at construction — so building a client stays synchronous. */
+    /**
+     * Resolved per enqueue, not at construction — so building a client stays synchronous.
+     *
+     * This goes through {@link ClientRegistry.resolve}, the SAME chain (mapping, else deriver, else
+     * throw) the RPC client runs. Cloud Tasks does not go through `ProxyClient.resolveBaseUrl()`, so
+     * it has to reach the chain itself — otherwise enqueue targets drift from call targets.
+     */
     resolveUrl(): Promise<string>;
 }

package/src/TaskClientConfig.js

@@ -1,7 +1,7 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.TaskClientConfig = void 0;
-const gcp_identity_1 = require("@webpieces/gcp-identity");
+const core_util_1 = require("@webpieces/core-util");
 /**
  * Per-client STATE for a Cloud Tasks enqueue client — nothing else.
  *
@@ -21,9 +21,15 @@ class TaskClientConfig {
     svcName) {
         this.svcName = svcName;
     }
-    /** Resolved per enqueue, not at construction — so building a client stays synchronous. */
+    /**
+     * Resolved per enqueue, not at construction — so building a client stays synchronous.
+     *
+     * This goes through {@link ClientRegistry.resolve}, the SAME chain (mapping, else deriver, else
+     * throw) the RPC client runs. Cloud Tasks does not go through `ProxyClient.resolveBaseUrl()`, so
+     * it has to reach the chain itself — otherwise enqueue targets drift from call targets.
+     */
     resolveUrl() {
-        return (0, gcp_identity_1.resolveServiceUrl)(this.svcName);
+        return core_util_1.ClientRegistry.resolve(this.svcName);
     }
 }
 exports.TaskClientConfig = TaskClientConfig;

package/src/TaskClientConfig.js.map

@@ -1 +1 @@
-{"version":3,"file":"TaskClientConfig.js","sourceRoot":"","sources":["../../../../../packages/cloud/cloudtasks-client/src/TaskClientConfig.ts"],"names":[],"mappings":";;;AAAA,0DAA4D;AAK5D;;;;;;GAMG;AACH,MAAa,gBAAgB;IAQL;IAPpB;IACI;;;;;OAKG;IACa,OAAe;QAAf,YAAO,GAAP,OAAO,CAAQ;IAChC,CAAC;IAEJ,0FAA0F;IAC1F,UAAU;QACN,OAAO,IAAA,gCAAiB,EAAC,IAAI,CAAC,OAAO,CAAC,CAAC;IAC3C,CAAC;CACJ;AAfD,4CAeC","sourcesContent":["import { resolveServiceUrl } from '@webpieces/gcp-identity';\n\n/** Constructor whose prototype is T (the abstract @PubSub API class). */\nexport type ApiPrototype<T> = Function & { prototype: T };\n\n/**\n * Per-client STATE for a Cloud Tasks enqueue client — nothing else.\n *\n * Collaborators (TaskInvoker, RequestContextHeaders) are NOT config: they are dependencies of\n * {@link ClientCloudTasksFactory} and shared by every client it builds. This is the fire-and-forget\n * twin of http-client-node's ClientConfig, and takes the same single field.\n */\nexport class TaskClientConfig {\n    constructor(\n        /**\n         * The service name. On GCP the URL is DERIVED from it (same project, same region — the Cloud\n         * Run service name, so you maintain no URL table), which works across demo/qa/prod. Anything\n         * the derivation cannot describe — a localhost port, another region/project, a non-Cloud-Run\n         * host — is a `ClientRegistry` mapping registered at startup, NOT a per-client URL.\n         */\n        public readonly svcName: string,\n    ) {}\n\n    /** Resolved per enqueue, not at construction — so building a client stays synchronous. */\n    resolveUrl(): Promise<string> {\n        return resolveServiceUrl(this.svcName);\n    }\n}\n"]}
+{"version":3,"file":"TaskClientConfig.js","sourceRoot":"","sources":["../../../../../packages/cloud/cloudtasks-client/src/TaskClientConfig.ts"],"names":[],"mappings":";;;AAAA,oDAAsD;AAKtD;;;;;;GAMG;AACH,MAAa,gBAAgB;IAQL;IAPpB;IACI;;;;;OAKG;IACa,OAAe;QAAf,YAAO,GAAP,OAAO,CAAQ;IAChC,CAAC;IAEJ;;;;;;OAMG;IACH,UAAU;QACN,OAAO,0BAAc,CAAC,OAAO,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC;IAChD,CAAC;CACJ;AArBD,4CAqBC","sourcesContent":["import { ClientRegistry } from '@webpieces/core-util';\n\n/** Constructor whose prototype is T (the abstract @PubSub API class). */\nexport type ApiPrototype<T> = Function & { prototype: T };\n\n/**\n * Per-client STATE for a Cloud Tasks enqueue client — nothing else.\n *\n * Collaborators (TaskInvoker, RequestContextHeaders) are NOT config: they are dependencies of\n * {@link ClientCloudTasksFactory} and shared by every client it builds. This is the fire-and-forget\n * twin of http-client-node's ClientConfig, and takes the same single field.\n */\nexport class TaskClientConfig {\n    constructor(\n        /**\n         * The service name. On GCP the URL is DERIVED from it (same project, same region — the Cloud\n         * Run service name, so you maintain no URL table), which works across demo/qa/prod. Anything\n         * the derivation cannot describe — a localhost port, another region/project, a non-Cloud-Run\n         * host — is a `ClientRegistry` mapping registered at startup, NOT a per-client URL.\n         */\n        public readonly svcName: string,\n    ) {}\n\n    /**\n     * Resolved per enqueue, not at construction — so building a client stays synchronous.\n     *\n     * This goes through {@link ClientRegistry.resolve}, the SAME chain (mapping, else deriver, else\n     * throw) the RPC client runs. Cloud Tasks does not go through `ProxyClient.resolveBaseUrl()`, so\n     * it has to reach the chain itself — otherwise enqueue targets drift from call targets.\n     */\n    resolveUrl(): Promise<string> {\n        return ClientRegistry.resolve(this.svcName);\n    }\n}\n"]}