Merge branch 'main' into copilot/fix-eslint-violations-icon-accessibility

Author: alexwizp

.agents/skills/scout-api-testing/SKILL.md

@@ -94,7 +94,7 @@ Tests then import `apiTest` from the local fixtures: `import { apiTest } from '.
 - Use either `--config` or `--testFiles` (they are mutually exclusive).
 - Run by config: `node scripts/scout.js run-tests --arch stateful --domain classic --config <module-root>/test/scout*/api/playwright.config.ts` (or `.../api/parallel.playwright.config.ts` for parallel API runs)
 - Run by file/dir (Scout derives the right `playwright.config.ts` vs `parallel.playwright.config.ts`): `node scripts/scout.js run-tests --arch stateful --domain classic --testFiles <module-root>/test/scout*/api/tests/my.spec.ts`
-- For faster iteration, start servers once in another terminal: `node scripts/scout.js start-server --arch stateful --domain classic [--serverConfigSet <configSet>]`, then run Playwright directly: `npx playwright test --config <...> --project local --grep <tag>`.
+- For faster iteration, start servers once in another terminal: `node scripts/scout.js start-server --arch stateful --domain classic [--serverConfigSet <configSet>]`, then run Playwright directly: `node scripts/playwright test --config <...> --project local --grep <tag>`.
 - `run-tests` auto-detects custom config sets from `.../test/scout_<name>/...` paths.
 - `start-server` has no Playwright config to inspect, so pass `--serverConfigSet <name>` when your tests require a custom config set.
 - Debug: `SCOUT_LOG_LEVEL=debug`

.agents/skills/scout-migrate-from-ftr/SKILL.md

@@ -64,7 +64,7 @@ Once execution is complete, run the new Scout tests and fix failures until they
 For faster feedback during the loop, start the test servers once and reuse them across iterations:
 
 1. Start servers (one-time): `node scripts/scout.js start-server --stateful --serverConfigSet <configSet>` (or `--serverless <project>`).
-2. Run the specs per iteration: `npx playwright test --config <playwright.config.ts> <test-file>`.
+2. Run the specs per iteration: `node scripts/playwright test --config <playwright.config.ts> <test-file>`.
 
 Falling back to `node scripts/scout.js run-tests` works but restarts the servers each time, which is much slower for iterative debugging.
 

.agents/skills/scout-ui-testing/SKILL.md

@@ -113,10 +113,10 @@ test('creates and verifies a dashboard', async ({ pageObjects, page }) => {
 - Use either `--config` or `--testFiles` (they are mutually exclusive).
 - Run by config: `node scripts/scout.js run-tests --arch stateful --domain classic --config <module-root>/test/scout*/ui/playwright.config.ts` (or `.../ui/parallel.playwright.config.ts` for parallel UI)
 - Run by file/dir (Scout derives the right `playwright.config.ts` vs `parallel.playwright.config.ts`): `node scripts/scout.js run-tests --arch stateful --domain classic --testFiles <module-root>/test/scout*/ui/tests/my.spec.ts`
-- For faster iteration, start servers once in another terminal: `node scripts/scout.js start-server --arch stateful --domain classic [--serverConfigSet <configSet>]`, then run Playwright directly: `npx playwright test --config <...> --project local --grep <tag> --headed`.
+- For faster iteration, start servers once in another terminal: `node scripts/scout.js start-server --arch stateful --domain classic [--serverConfigSet <configSet>]`, then run Playwright directly: `node scripts/playwright test --config <...> --project local --grep <tag> --headed`.
 - `run-tests` auto-detects custom config sets from `.../test/scout_<name>/...` paths.
 - `start-server` has no Playwright config to inspect, so pass `--serverConfigSet <name>` when your tests require a custom config set.
-- Debug: `SCOUT_LOG_LEVEL=debug`, or `npx playwright test --config <...> --project local --ui`
+- Debug: `SCOUT_LOG_LEVEL=debug`, or `node scripts/playwright test --config <...> --project local --ui`
 
 ## CI enablement
 

.buildkite/ftr-manifests/ftr_vectordb_serverless_configs.yml

@@ -1,6 +1,15 @@
-# VectorDB project FTR configs.
-# Placeholder — fill in once vectordb-specific FTR configs exist.
-# Reference: ftr_workplace_ai_serverless_configs.yml
-disabled: []
+disabled:
+  # Base config files, only necessary to inform config finding script
+  - x-pack/platform/test/serverless/functional/config.vectordb.base.ts
+
+  # Empty configs
+  - x-pack/solutions/vectordb/test/serverless/functional/configs/config.feature_flags.ts
+  - x-pack/solutions/vectordb/test/serverless/api_integration/configs/config.feature_flags.ts
+
 defaultQueue: 'n2-4-spot'
-enabled: []
+enabled:
+  - x-pack/solutions/vectordb/test/serverless/api_integration/configs/config.ts
+  - x-pack/platform/test/serverless/api_integration/configs/vectordb/config.group1.ts
+  - x-pack/solutions/vectordb/test/serverless/functional/configs/config.ts
+  - x-pack/platform/test/serverless/functional/configs/vectordb/config.config_compat_mode.ts
+  - x-pack/platform/test/serverless/functional/configs/vectordb/config.group1.ts

.buildkite/pipeline-resource-definitions/kibana-version-bump.yml

@@ -42,5 +42,5 @@ spec:
           access_level: BUILD_AND_READ
         everyone:
           access_level: READ_ONLY
-        release-eng:
+        artifact-management:
           access_level: BUILD_AND_READ

.buildkite/pipeline-utils/scout/test_distribution_strategies.ts

@@ -58,7 +58,7 @@ async function distributeScoutTestsOnLanes() {
   }
 
   const steps: BuildkiteCommandStep[] = [];
-  const loadIDsByStepKey: Record<string, string[]> = {};
+  const loadInfoByStepKey: Record<string, { label: string; loadIDs: string[] }> = {};
   const testLaneLoadsFilePath = path.relative(getKibanaDir(), SCOUT_TEST_LANE_LOADS_PATH);
 
   testTracksDefinitionPaths
@@ -72,8 +72,6 @@ async function distributeScoutTestsOnLanes() {
       // Define the effective lane number. `lane.number` is only accurate in reference to the originating test track
       const effectiveLaneNumber = steps.length + 1;
 
-      const stepKey = `scout_test_lane_${effectiveLaneNumber}`;
-
       const laneEnv = {
         SCOUT_TEST_LANE_LOADS_PATH: testLaneLoadsFilePath,
         SCOUT_TEST_LANE_NUMBER: `${effectiveLaneNumber}`,
@@ -91,10 +89,13 @@ async function distributeScoutTestsOnLanes() {
         ...collectEnvFromLabels(),
       };
 
+      const stepKey = `scout_test_lane_${effectiveLaneNumber}`;
+      const stepLabel = `Scout Lane #${effectiveLaneNumber} - ${testTarget.arch}-${testTarget.domain} / ${server.configSet}`;
+
       // Agent that will do the actual work of running the test loads
       steps.push({
-        key: `scout_test_lane_${effectiveLaneNumber}`,
-        label: `Scout Lane #${effectiveLaneNumber} - ${testTarget.arch}-${testTarget.domain} / ${server.configSet}`,
+        key: stepKey,
+        label: stepLabel,
         command: '.buildkite/scripts/steps/test/scout/run_test_lane.sh',
         timeout_in_minutes: 60,
         agents: expandAgentQueue(lane.metadata.buildkite.agentQueue),
@@ -107,8 +108,8 @@ async function distributeScoutTestsOnLanes() {
         },
       });
 
-      // Lane load IDs to be referenced by the agent
-      loadIDsByStepKey[stepKey] = lane.loads;
+      // Lane load information to be referenced by the agent (IDs in particular)
+      loadInfoByStepKey[stepKey] = { label: stepLabel, loadIDs: lane.loads };
     });
 
   if (steps.length === 0) {
@@ -138,7 +139,7 @@ async function distributeScoutTestsOnLanes() {
   );
 
   // Write the test lane load IDs to disk in preparation of uploading as an artifact
-  fs.writeFileSync(testLaneLoadsFilePath, JSON.stringify(loadIDsByStepKey));
+  fs.writeFileSync(testLaneLoadsFilePath, JSON.stringify(loadInfoByStepKey));
   bk.uploadArtifacts(testLaneLoadsFilePath);
 
   // Send it 🚀

.buildkite/pipelines/pull_request/post_build.yml

@@ -5,4 +5,15 @@ steps:
   - command: .buildkite/scripts/lifecycle/post_build.sh
     label: Post-Build
     agents:
-      machineType: n2-standard-2
+      provider: k8s
+      image: docker.elastic.co/ci-agent-images/kibana/ci-minimal
+      imageUID: 1000
+    plugins:
+      - sparse-checkout#v1.6.0:
+          paths:
+            - .buildkite
+            - .node-version
+            - package.json
+            - tsconfig.base.json
+            - versions.json
+          cleanup_sparse_state: true

.buildkite/pipelines/security_solution_quality_gate/mki_periodic/mki_periodic_ai4dsoc.yml

@@ -15,6 +15,8 @@ steps:
         # TODO : Revise the timeout when the pipeline will be officially integrated with the quality gate.
         timeout_in_minutes: 300
         parallelism: 1
+        soft_fail:
+          - exit_status: 101
 
   - group: "API MKI - AI4DSOC"
     key: api_test_ai4dsoc
@@ -32,6 +34,8 @@ steps:
           automatic:
             - exit_status: "1"
               limit: 2
+        soft_fail:
+          - exit_status: 101
 
       - label: Running ai4dsoc_nlp_cleanup_task:qa:serverless
         command: .buildkite/scripts/pipelines/security_solution_quality_gate/api_integration/api-integration-tests.sh ai4dsoc_nlp_cleanup_task:qa:serverless
@@ -46,3 +50,5 @@ steps:
           automatic:
             - exit_status: "1"
               limit: 2
+        soft_fail:
+          - exit_status: 101

.buildkite/pipelines/security_solution_quality_gate/mki_periodic/mki_periodic_defend_workflows.yml

@@ -14,6 +14,8 @@ steps:
           diskSizeGb: 120
         timeout_in_minutes: 300
         parallelism: 5
+        soft_fail:
+          - exit_status: 101
 
   - group: "Osquery MKI - Defend Workflows"
     key: cypress_test_osquery_defend_workflows
@@ -30,6 +32,8 @@ steps:
           diskSizeGb: 120
         timeout_in_minutes: 300
         parallelism: 3
+        soft_fail:
+          - exit_status: 101
 
   - group: "API MKI - Defend Workflows"
     key: api_test_defend_workflows
@@ -108,6 +112,8 @@ steps:
           automatic:
             - exit_status: "1"
               limit: 1
+        soft_fail:
+          - exit_status: 101
 
       - label: "API MKI - edr_workflows:resolver:qa:serverless"
         command: .buildkite/scripts/pipelines/security_solution_quality_gate/api_integration/api-integration-tests.sh edr_workflows:resolver:qa:serverless
@@ -123,6 +129,8 @@ steps:
           automatic:
             - exit_status: "1"
               limit: 1
+        soft_fail:
+          - exit_status: 101
 
       - label: "API MKI - edr_workflows:response_actions:qa:serverless"
         command: .buildkite/scripts/pipelines/security_solution_quality_gate/api_integration/api-integration-tests.sh edr_workflows:response_actions:qa:serverless
@@ -138,3 +146,5 @@ steps:
           automatic:
             - exit_status: "1"
               limit: 1
+        soft_fail:
+          - exit_status: 101