The servers of a Legend deployment hosting the Cube page, as its config names them (PLAN §11.18): the engine, and each of the others only where the deployment has one. Legend Query and Legend Analytics each read theirs from their own config.

interface LegendCubeHostConfig {
    deploymentNameServiceUrl?: string;
    depotServerUrl?: string;
    engine: V1_EngineServerClientConfig;
    enterpriseStereotype?: { profile: string; value: string };
    getPreferredEnvironment?: () => undefined | string;
    lakehouseContractUrl?: string;
    lakehousePlatformUrl?: string;
    marketplaceApplicationUrl?: string;
    marketplaceProductionParallelUrl?: string;
    marketplaceServerUrl?: string;
}

Properties

deploymentNameServiceUrl?: string

The engine path of the Legend user service naming producer deployments, as Marketplace configures it

depotServerUrl?: string

Published projects (PLAN §6.3) and, with a lakehouse, the data products' models

engine: V1_EngineServerClientConfig
enterpriseStereotype?: { profile: string; value: string }

The stereotype marking access point groups open to everyone, as Studio and Marketplace configure it

getPreferredEnvironment?: () => undefined | string

The lakehouse environment the host remembers for the viewer

lakehouseContractUrl?: string

The lakehouse's contracts: data products need it, and a depot (PLAN §6.8)

lakehousePlatformUrl?: string

The lakehouse platform, which names the ingest servers: ingest data sets need it (PLAN §6.7)

marketplaceApplicationUrl?: string

Legend Marketplace, which a production data product links to

marketplaceProductionParallelUrl?: string

Legend Marketplace's production-parallel deployment, which a production-parallel data product links to

marketplaceServerUrl?: string

The marketplace server, whose search the data product tab uses