← API reference
CANONICAL TYPE REFERENCE

FolderBindingKind

Which transport a folder's bytes live on: CONTROL_CLOUD (the platform's own cloud file store), STORAGE_BACKEND (a tenant-configured S3 / hostPath backend), or CONTROLLER (a filesystem on an edge controller, reached over file RPC). The kind determines which reference ID and rootPath shape apply.

CONTROL_CLOUD

The bytes live in ControlApp's own cloud file store, which the platform operates on the tenant's behalf. Control must configure a storage account; storageCapabilities and testFolder report read-only prerequisites. The store mints its own storage keys, so this is the one kind whose rootPath carries no meaning and is ignored.

STORAGE_BACKEND

The bytes live under a path inside one of the tenant's own StorageBackend rows, so the tenant supplies the account and credentials. storageBackendId names the backend and rootPath is a relative prefix within it, never starting with a slash.

CONTROLLER

The bytes live on the filesystem of an edge controller and are reached over file RPC rather than any cloud API, so the folder is only usable while that controller is online. controllerId names it and rootPath is an absolute path on that machine.

View exact SDL
"""
Which transport a folder's bytes live on: CONTROL_CLOUD (the platform's own cloud file store), STORAGE_BACKEND (a tenant-configured S3 / hostPath backend), or CONTROLLER (a filesystem on an edge controller, reached over file RPC). The kind determines which reference ID and rootPath shape apply.
"""
enum FolderBindingKind {
  """
  The bytes live in ControlApp's own cloud file store, which the platform operates on the tenant's behalf. Control must configure a storage account; storageCapabilities and testFolder report read-only prerequisites. The store mints its own storage keys, so this is the one kind whose rootPath carries no meaning and is ignored.
  """
  CONTROL_CLOUD
  """
  The bytes live under a path inside one of the tenant's own StorageBackend rows, so the tenant supplies the account and credentials. storageBackendId names the backend and rootPath is a relative prefix within it, never starting with a slash.
  """
  STORAGE_BACKEND
  """
  The bytes live on the filesystem of an edge controller and are reached over file RPC rather than any cloud API, so the folder is only usable while that controller is online. controllerId names it and rootPath is an absolute path on that machine.
  """
  CONTROLLER
}

One stable address across all schema views. Follow a field’s type to explore connections between domains.