Optional ReadonlydeploymentThe engine path of the Legend user service naming producer deployments, as Marketplace configures it
Optional ReadonlydepotPublished projects (PLAN §6.3) and, with a lakehouse, the data products' models
ReadonlyengineOptional ReadonlyenterpriseThe stereotype marking access point groups open to everyone, as Studio and Marketplace configure it
Optional ReadonlygetThe lakehouse environment the host remembers for the viewer
Optional ReadonlylakehouseThe lakehouse's contracts: data products need it, and a depot (PLAN §6.8)
Optional ReadonlylakehouseThe lakehouse platform, which names the ingest servers: ingest data sets need it (PLAN §6.7)
Optional ReadonlymarketplaceLegend Marketplace, which a production data product links to
Optional ReadonlymarketplaceLegend Marketplace's production-parallel deployment, which a production-parallel data product links to
Optional ReadonlymarketplaceThe marketplace server, whose search the data product tab uses
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.