Issue 6892: workerManager.registerWorker: treat test-provisioner-id s…

…pecially

changelog/issue-6892.md

@@ -0,0 +1,8 @@
+audience: developers
+level: minor
+reference: issue 6892
+---
+Worker Manager now special-cases `registerWorker` API calls with provisionerId
+`test-provisioner-id`. It responds as if the call was successful with fake
+`credentials`, `expiry`, and `secret`, but the real `workerConfig`, if it
+exists.

services/worker-manager/schemas/v1/worker-full.yml

@@ -9,7 +9,9 @@ properties:
   workerGroup:
     title: Worker group
     type: string
-    description: Worker group to which this worker belongs
+    description: |
+      Worker group to which this worker belongs. The special value
+      `test-worker-group` is reserved for use by tests.
     minLength: {$const: identifier-min-length}
     maxLength: {$const: identifier-max-length}
     pattern: {$const: identifier-pattern}

services/worker-manager/src/api.js

@@ -820,6 +820,19 @@ builder.declare({
       `Worker pool ${workerPoolId} not associated with provider ${providerId}`, {});
   }
 
+  if (workerPoolId.startsWith("test-provisioner-id/")) {
+    return res.reply({
+      expires: "2000-00-00T00:00:00Z",
+      credentials: {
+        accessToken: "test-access-token",
+        certificate: "test-certificate",
+        clientId: "test-client-id",
+	  },
+      workerConfig,
+      secret: "test-secret",
+    });
+  }
+
   const worker = await Worker.get(this.db, { workerPoolId, workerGroup, workerId });
   if (!worker) {
     this.monitor.debug({