@edgible-team/sdk
    Preparing search index...

    Function assertComposeWorkloadsValid

    • The SHIPPING-path gate: throw on the first severity: 'error' finding in any of the application's compose workloads. StacksClient.deploy calls this immediately before it creates or updates an application, so a document that cannot possibly run fails the deploy loudly instead of reporting converged — while status/diff/teardown/validate, which ship nothing, stay usable.

      Only base64:-embedded compose bytes are inspected. A bare path has not been read (that is loadStackFile's job, tier 2) and a composeArtifact bundle's bytes never reach the client at all — both are skipped, so this is fast local feedback, never a server-enforced guarantee.

      By the time the gate runs, the bytes are base64: and the path they were read from is gone from the document. composeSources is the loader's record of that path per (application, workload) — loadStackFile returns it — so the thrown details.composeFile NAMES the file the operator has to fix. A workload with no recorded source (inline base64 in the stack file, or a caller that never went through the loader) is named <embedded compose document>.

      Parameters

      Returns void

      ComposeValidationError STACK_COMPOSE_PARSE_FAILED / STACK_COMPOSE_INVALID.