@camunda/e2e-test-suite 0.0.832 → 0.0.833

package/dist/utils/consoleApiHelpers.d.ts

@@ -1,4 +1,5 @@
 import { Page } from '@playwright/test';
 export declare function deleteClusterViaApi(page: Page, clusterName: string): Promise<void>;
 export declare function createClusterViaApi(page: Page, clusterName: string, region?: string): Promise<string>;
+export declare function ensureClusterViaApi(page: Page, clusterName: string, region?: string): Promise<string>;
 export declare function waitForClusterHealthyViaApi(page: Page, clusterUuid: string, timeoutMs?: number): Promise<void>;

package/dist/utils/consoleApiHelpers.js

@@ -1,6 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.waitForClusterHealthyViaApi = exports.createClusterViaApi = exports.deleteClusterViaApi = void 0;
+exports.waitForClusterHealthyViaApi = exports.ensureClusterViaApi = exports.createClusterViaApi = exports.deleteClusterViaApi = void 0;
 const test_1 = require("@playwright/test");
 const sleep_1 = require("./sleep");
 const PLAN_TYPE_ID = '574cde5f-54ae-43c1-851a-e6fb4f03423a';
@@ -125,6 +125,28 @@ async function createClusterViaApi(page, clusterName, region = 'GCP') {
     return clusterId;
 }
 exports.createClusterViaApi = createClusterViaApi;
+async function ensureClusterViaApi(page, clusterName, region = 'GCP') {
+    // Versions with more than one Tasklist-mode Playwright project (e.g. 8.8,
+    // 8.9's chromium-v1/chromium-v2) run test-setup.spec.ts once per project,
+    // concurrently, against the same org -- and both target a cluster with
+    // this same name. Deleting-then-recreating unconditionally here would race
+    // with the sibling project's setup: whichever one runs its delete second
+    // rips out the cluster the other project already started using, silently
+    // orphaning any process instances/jobs created on it in the meantime.
+    //
+    // Each PR/nightly run gets a brand-new, empty org (see the
+    // create-organization/delete-organization jobs), so within a single run a
+    // cluster with this name can only mean one thing: the sibling project's
+    // setup already created it. Adopt it instead of destroying it -- whichever
+    // project's setup gets here first "wins" and creates it, the other one
+    // just reuses it.
+    const existing = await findClusterByName(page, clusterName);
+    if (existing) {
+        return existing.uuid;
+    }
+    return createClusterViaApi(page, clusterName, region);
+}
+exports.ensureClusterViaApi = ensureClusterViaApi;
 async function waitForClusterHealthyViaApi(page, clusterUuid, timeoutMs = 1500000) {
     const orgId = getOrgId();
     const url = `${getConsoleBaseUrl()}/api/orgs/${orgId}/clusters/${clusterUuid}`;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camunda/e2e-test-suite",
-  "version": "0.0.832",
+  "version": "0.0.833",
   "description": "End-to-end test helpers for Camunda 8",
   "repository": {
     "type": "git",