What the application hosting the Cube page gives it (PLAN §3.5, Settled before M1.8). The host chooses the engine and the models; Cube keeps no auth, config or telemetry of its own and uses the host's application store for commands, user data, the clipboard, the theme, notifications, alerts and telemetry.

Implemented by

Properties

applicationStore: GenericLegendApplicationStore
connectionExplorer?: CubeConnectionExplorer

Reads the databases behind direct connections (PLAN §6.8); without one, the source picker offers no database connection

dataProductCatalog?: CubeDataProductCatalog

The deployed data products (PLAN §6.8); without one, the source dialog offers no data products

engine: CubeEngine
engineClientSettings?: CubeEngineClientSettings

The engine URL and request compression its engine clients share, which Dev Settings changes (PLAN §11.16); without them, Dev Settings can't change either

ingestCatalog?: CubeIngestCatalog

The deployed ingest definitions (PLAN §6.7); without one, the source dialog offers no ingest data sets

modelCatalog: LocalModelCatalog
offersSampleData?: boolean

Whether the page offers Cube's sample data: the source dialog's Sample Data tab and the Examples. Offered unless the host says no, as Studio does, where a cube reads only the project's ingest definitions

project?: CubeHostProject

The one project whose own sources the page reads, e.g. the one Studio edits: the source dialog lists its ingest definitions and data products by name and path, with no class, deployment or search across the platform, and says which lakehouse runtime its runs use

projectCatalog?: CubeProjectCatalog

The published projects in the host's depot (PLAN §6.3); without one, the source dialog offers no projects

serviceCatalog?: CubeServiceCatalog

The deployed services (PLAN §6.4), in progress; without one, the source dialog offers no services