SP-925: Add PLATFORM_SERVICE validation layer to config validate

docs/user-guide/config-commands.md

@@ -204,17 +204,21 @@ The `--layers` option selects which validation layers to run. Multiple layers ca
 | `SCHEMA` | Asset-schema conformance of each node's `configuration` field — required properties, enum values, type checks, conditional schemas. | Asset registry |
 | `BUSINESS` | Asset-type-specific business rules — for `SEMANTIC_MODEL`, e.g. PQL parsing, data-model availability, KPI uniqueness. Rules live in the owning asset service. | Owning asset service (e.g. `cloud-semantic-layer` for Knowledge Models) |
 | `PACKAGE_SETTINGS` | Package-level configuration rules — package dependencies, package variable definitions, variable assignments such as Studio data models, and flavor-specific package settings for Studio/OCDM packages. | Pacman plus flavor-specific services |
+| `PIG_SEMANTICS` | Semantic-model validation delegated to the Process Intelligence Graph semantic-layer runtime (PIG-SL), surfacing the `list-problems` findings the live service reports for Knowledge Models. | Semantic layer (`cloud-semantic-layer`) |
+| `DATA_PIPELINES` | Validation delegated to the data-pipeline platform service for the package's data-integration assets. | Data pipeline service |
 
-Currently `SCHEMA`, `BUSINESS`, and `PACKAGE_SETTINGS` are the layers accepted by the Pacman API. Other values are rejected with a `400 layers.unsupported` error.
+`SCHEMA`, `BUSINESS`, `PACKAGE_SETTINGS`, `PIG_SEMANTICS`, and `DATA_PIPELINES` are the layers accepted by the Pacman API. Other values are rejected with a `400 layers.unsupported` error.
 
 To run all layers:
 
 ```bash
-content-cli config package validate --packageKey <packageKey> --layers SCHEMA BUSINESS PACKAGE_SETTINGS
+content-cli config package validate --packageKey <packageKey> --layers SCHEMA BUSINESS PACKAGE_SETTINGS PIG_SEMANTICS DATA_PIPELINES
 ```
 
 Use `PACKAGE_SETTINGS` when you need to verify that the package's own settings are usable in the destination team before continuing authoring or import work. It reports issues such as missing dependency versions, duplicate dependency or variable keys, blank variable keys/types, missing Studio data model assignments, and OCDM package-settings problems when the corresponding backend validation is enabled.
 
+Use `PIG_SEMANTICS` and `DATA_PIPELINES` to additionally validate the package against the live platform services that own its assets: `PIG_SEMANTICS` runs the Process Intelligence Graph semantic-layer checks (for example for Knowledge Models) and `DATA_PIPELINES` runs the data-pipeline service checks for the package's data-integration assets. Both delegate validation to the owning service rather than running in-process; which services take part, and how their findings map to severities, is declared by platform-service descriptors.
+
 ### Validate Specific Nodes
 
 By default, every node in the package's staging version is validated. To restrict the scope to a subset of nodes, use `--nodeKeys`:
@@ -228,7 +232,7 @@ content-cli config package validate --packageKey <packageKey> --nodeKeys node-ke
 Use `--json` to write the full validation report to a JSON file in the current working directory instead of printing it to the console:
 
 ```bash
-content-cli config package validate --packageKey <packageKey> --layers SCHEMA BUSINESS PACKAGE_SETTINGS --json
+content-cli config package validate --packageKey <packageKey> --layers SCHEMA BUSINESS PACKAGE_SETTINGS PIG_SEMANTICS DATA_PIPELINES --json
 ```
 
 The filename is printed on success:
@@ -248,7 +252,7 @@ interface ValidationReport {
 }
 
 interface ValidationResult {
-    layer: "SCHEMA" | "BUSINESS" | "PACKAGE_SETTINGS";
+    layer: "SCHEMA" | "BUSINESS" | "PACKAGE_SETTINGS" | "PIG_SEMANTICS" | "DATA_PIPELINES";
     severity: "ERROR" | "WARNING" | "INFO";
     nodeKey: string;
     assetType: string;

src/commands/configuration-management/module.ts

@@ -84,7 +84,7 @@ class Module extends IModule {
             .requiredOption("--packageKey <packageKey>", "Key of the package to validate")
             .option(
                 "--layers <layers...>",
-                "Validation layers to run. Allowed values: SCHEMA, BUSINESS, PACKAGE_SETTINGS (can be combined, e.g. --layers SCHEMA BUSINESS PACKAGE_SETTINGS). Defaults to SCHEMA.",
+                "Validation layers to run. Allowed values: SCHEMA, BUSINESS, PACKAGE_SETTINGS, PIG_SEMANTICS, DATA_PIPELINES (can be combined, e.g. --layers SCHEMA BUSINESS PACKAGE_SETTINGS PIG_SEMANTICS DATA_PIPELINES). Defaults to SCHEMA.",
                 ["SCHEMA"]
             )
             .option("--nodeKeys <nodeKeys...>", "Specific node keys to validate (default: all nodes)")
@@ -103,7 +103,7 @@ class Module extends IModule {
             .requiredOption("--packageKey <packageKey>", "Key of the package to validate")
             .option(
                 "--layers <layers...>",
-                "Validation layers to run. Allowed values: SCHEMA, BUSINESS, PACKAGE_SETTINGS (can be combined, e.g. --layers SCHEMA BUSINESS PACKAGE_SETTINGS). Defaults to SCHEMA.",
+                "Validation layers to run. Allowed values: SCHEMA, BUSINESS, PACKAGE_SETTINGS, PIG_SEMANTICS, DATA_PIPELINES (can be combined, e.g. --layers SCHEMA BUSINESS PACKAGE_SETTINGS PIG_SEMANTICS DATA_PIPELINES). Defaults to SCHEMA.",
                 ["SCHEMA"]
             )
             .option("--nodeKeys <nodeKeys...>", "Specific node keys to validate (default: all nodes)")

tests/commands/configuration-management/config-validate.spec.ts

@@ -104,4 +104,80 @@ describe("Config validate", () => {
         expect(allMessages).toContain("Validation result: VALID");
         expect(allMessages).toContain("Errors: 0");
     })
+
+    it("Should send PIG_SEMANTICS and DATA_PIPELINES layers in request body when combined with other layers", async () => {
+        const response: SchemaValidationResponse = {
+            packageKey: "my-package",
+            valid: true,
+            summary: { errors: 0, warnings: 0, info: 0 },
+            results: []
+        };
+
+        mockAxiosPost(VALIDATE_URL, response);
+
+        await new PackageValidationService(testContext).validatePackage(
+            "my-package",
+            ["SCHEMA", "BUSINESS", "PACKAGE_SETTINGS", "PIG_SEMANTICS", "DATA_PIPELINES"],
+            null,
+            false
+        );
+
+        expect(mockedPostRequestBodyByUrl.get(VALIDATE_URL)).toEqual(
+            JSON.stringify({ layers: ["SCHEMA", "BUSINESS", "PACKAGE_SETTINGS", "PIG_SEMANTICS", "DATA_PIPELINES"] })
+        );
+    })
+
+    it("Should render PIG_SEMANTICS findings in human-readable output", async () => {
+        const response: SchemaValidationResponse = {
+            packageKey: "my-package",
+            valid: false,
+            summary: { errors: 0, warnings: 1, info: 0 },
+            results: [{
+                layer: "PIG_SEMANTICS",
+                severity: "WARNING",
+                nodeKey: "my-knowledge-model",
+                assetType: "SEMANTIC_MODEL",
+                path: "$.dataModel",
+                code: "DATA_MODEL_NOT_FOUND",
+                message: "Referenced data model is not available in the target team"
+            }]
+        };
+
+        mockAxiosPost(VALIDATE_URL, response);
+
+        await new PackageValidationService(testContext).validatePackage("my-package", ["PIG_SEMANTICS"], null, false);
+
+        const allMessages = loggingTestTransport.logMessages.map(m => m.message).join("\n");
+        expect(allMessages).toContain("Validation result: INVALID");
+        expect(allMessages).toContain("Warnings: 1");
+        expect(allMessages).toContain("my-knowledge-model (SEMANTIC_MODEL)");
+        expect(allMessages).toContain("DATA_MODEL_NOT_FOUND");
+    })
+
+    it("Should write DATA_PIPELINES findings to the JSON report when json flag is set", async () => {
+        const response: SchemaValidationResponse = {
+            packageKey: "my-package",
+            valid: false,
+            summary: { errors: 1, warnings: 0, info: 0 },
+            results: [{
+                layer: "DATA_PIPELINES",
+                severity: "ERROR",
+                nodeKey: "my-data-pool",
+                assetType: "DATA_POOL",
+                path: "$.connection",
+                code: "CONNECTION_NOT_FOUND",
+                message: "Referenced connection is not available in the target team"
+            }]
+        };
+
+        mockAxiosPost(VALIDATE_URL, response);
+
+        await new PackageValidationService(testContext).validatePackage("my-package", ["DATA_PIPELINES"], null, true);
+
+        expect(mockWriteFileSync).toHaveBeenCalledWith(
+            expect.stringMatching(/config_validate_report_.+\.json$/),
+            JSON.stringify(response),
+            { encoding: "utf-8", mode: 0o600 }
+        );
+    })
 })