@omen.foundation/node-microservice-runtime 0.1.93 → 0.1.95

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@omen.foundation/node-microservice-runtime",
-  "version": "0.1.93",
+  "version": "0.1.95",
   "description": "Beamable microservice runtime for Node.js/TypeScript services.",
   "type": "module",
   "main": "dist/index.js",

package/scripts/publish-service.mjs

@@ -1015,8 +1015,13 @@ async function updateManifest({
     console.error(`[beamo-node]   Headers:`, JSON.stringify(publishHeaders, null, 2));
     console.error(`[beamo-node]   Service: ${serviceId}`);
     console.error(`[beamo-node]   CID: ${cid}`);
-    console.error(`[beamo-node]   PID: ${pid}`);
+    console.error(`[beamo-node]   Realm PID (from X-BEAM-SCOPE): ${pid}`);
     console.error(`[beamo-node]   Short Image ID: ${shortImageId}`);
+    console.error(`[beamo-node]   Expected Backend Check:`);
+    console.error(`[beamo-node]     - Backend will calculate imageNameMD5 using: rc.cid, rc.gameId, serviceName`);
+    console.error(`[beamo-node]     - Backend will check: {registryURI}/{imageNameMD5}/manifests/{imageId}`);
+    console.error(`[beamo-node]     - Backend will use headers: X-KS-PROJECTID: rc.projectId (from X-BEAM-SCOPE)`);
+    console.error(`[beamo-node]     - NOTE: rc.gameId might differ from realm PID if backend resolves it differently`);
     console.error(`[beamo-node]   Request Body:`, JSON.stringify(requestBody, null, 2));
     console.error(`[beamo-node]   Service Entry in Manifest:`, JSON.stringify(mappedServices.find(s => s.serviceName === serviceId), null, 2));
   }
@@ -1284,8 +1289,8 @@ async function main() {
       }
     }
     
-    // Use resolvedGamePid for registry URL and uniqueName - backend checks using game PID scope
-    // The pid variable might be a realm PID, but the backend expects game PID for registry operations
+    // Match C# CLI: GetDockerImageRegistryUri() uses realm PID from context (X-BEAM-SCOPE)
+    // uniqueName uses gamePid (matches backend's rc.gameId), but registry URL uses realm PID
     if (process.env.BEAMO_DEBUG === '1' || process.env.BEAMO_NODE_DEBUG === '1') {
       console.error(`[beamo-node] [STEP: Calculate Registry Path]`);
       console.error(`[beamo-node]   CID: ${cid}`);
@@ -1293,7 +1298,7 @@ async function main() {
       console.error(`[beamo-node]   Resolved Game PID: ${resolvedGamePid}`);
       console.error(`[beamo-node]   Service ID: ${serviceId}`);
     }
-    const registryUrl = await getRegistryUrl(apiHost, token, cid, resolvedGamePid);
+    const registryUrl = await getRegistryUrl(apiHost, token, cid, pid);
     const uniqueNameInput = `${cid}_${resolvedGamePid}_${serviceId}`;
     const uniqueName = md5Hex(uniqueNameInput).substring(0, 30);
     if (process.env.BEAMO_DEBUG === '1' || process.env.BEAMO_NODE_DEBUG === '1') {
@@ -1352,6 +1357,43 @@ async function main() {
     if (process.env.BEAMO_DEBUG === '1' || process.env.BEAMO_NODE_DEBUG === '1') {
       console.error(`[beamo-node]   ✓ Image verification passed`);
     }
+    
+    // CRITICAL: Before publishing, verify using the backend's expected gameId
+    // The backend resolves rc.gameId from the realm hierarchy, which might differ from our resolvedGamePid
+    // We need to check what the backend will actually use
+    if (process.env.BEAMO_DEBUG === '1' || process.env.BEAMO_NODE_DEBUG === '1') {
+      console.error(`[beamo-node] [STEP: Pre-Publish Backend Simulation]`);
+      console.error(`[beamo-node]   Simulating backend's imageNameMD5 calculation...`);
+      console.error(`[beamo-node]   Backend will use: rc.cid, rc.gameId (resolved from realm hierarchy), serviceName`);
+      console.error(`[beamo-node]   Our calculation used: cid=${cid}, gamePid=${resolvedGamePid}, serviceName=${serviceId}`);
+      console.error(`[beamo-node]   Our uniqueName: ${uniqueName}`);
+      console.error(`[beamo-node]   WARNING: If backend's rc.gameId differs from our resolvedGamePid, the check will fail!`);
+    }
+    
+    // Try to resolve what the backend's rc.gameId will be by making the same API call the backend would make
+    // The backend resolves gameId from the realm hierarchy when processing X-BEAM-SCOPE
+    try {
+      const backendGamePidCheck = await resolveGamePid(apiHost, token, cid, pid, null); // Force resolution
+      if (process.env.BEAMO_DEBUG === '1' || process.env.BEAMO_NODE_DEBUG === '1') {
+        console.error(`[beamo-node]   Backend's expected gameId (resolved from realm hierarchy): ${backendGamePidCheck}`);
+        if (backendGamePidCheck !== resolvedGamePid) {
+          console.error(`[beamo-node]   ⚠️  MISMATCH DETECTED!`);
+          console.error(`[beamo-node]     Our resolvedGamePid: ${resolvedGamePid}`);
+          console.error(`[beamo-node]     Backend's expected gameId: ${backendGamePidCheck}`);
+          console.error(`[beamo-node]     This will cause imageNameMD5 mismatch!`);
+          const backendUniqueNameInput = `${cid}_${backendGamePidCheck}_${serviceId}`;
+          const backendUniqueName = md5Hex(backendUniqueNameInput).substring(0, 30);
+          console.error(`[beamo-node]     Backend will check: ${registryUrl}${backendUniqueName}/manifests/${shortImageId}`);
+          console.error(`[beamo-node]     But we uploaded to: ${registryUrl}${uniqueName}/manifests/${shortImageId}`);
+        } else {
+          console.error(`[beamo-node]   ✓ Game PID matches - backend should find the image`);
+        }
+      }
+    } catch (error) {
+      if (process.env.BEAMO_DEBUG === '1' || process.env.BEAMO_NODE_DEBUG === '1') {
+        console.error(`[beamo-node]   Could not verify backend gameId resolution: ${error.message}`);
+      }
+    }
 
     // Step 7: Discover storage, components, and dependencies
     progress.start('Discovering storage objects and components');