Skip to main content
Components are optional services in your stack, such as fcrepo or Blazegraph, that can be switched on or off without rebuilding the whole project. sitectl delegates component management to the plugin for the active context, so the commands work across different stack types. See the components concept page for an explanation of what components are and how they work.

​
component

Components are optional stack features — such as Fcrepo or Blazegraph — that can be toggled on or off. sitectl dispatches component commands to the plugin associated with the active context. The plugin provides the component registry; sitectl provides a consistent entry point regardless of which stack you are working with. Use “sitectl component list” to show registered components, allowed dispositions, and any component-specific flags accepted by “sitectl component set”.

​
describe

Show the current state of each component registered by the active context’s plugin. Each component is reported as on, off, or drifted. A drifted component means the current project configuration does not match a complete supported disposition — run reconcile to review and bring it into alignment.

​
list

List components registered by the active context’s plugin, including allowed dispositions and component-specific set flags.

​
reconcile

Compare component-owned project configuration with .libops/site.yaml, print the complete reconciliation plan, and apply approved changes needed to restore the selected dispositions and settings. Unknown or unclassified changes block mutation. Destructive operations are identified in the plan. By default each component change requires confirmation. Pass --report to preview without changing files, or --yolo to skip confirmation after reviewing the same plan in automation.
A component shows as drifted when its component-owned project files do not match the disposition and settings recorded in .libops/site.yaml. Run reconcile --report to inspect every proposed operation, its target, and its risk without changing the project. Unknown components or changes that sitectl cannot classify block application instead of being guessed.

​
set

Set the desired disposition and settings of a named component, apply its component-owned project changes, and persist the reviewed intent in .libops/site.yaml for later validation and convergence. Prefix the component name with the plugin namespace to target it directly: sitectl component set isle/fcrepo off sitectl component set isle/blazegraph off All flags after “set” are forwarded to the plugin’s component set handler. Use “sitectl component set --help” or “sitectl component list <component>” to see component-specific flags.
After confirmation, set applies the component transformation and records the selected disposition and non-secret settings in .libops/site.yaml. Commit that file with the Compose project: it is the reviewable intent used by reconcile, validate, and verify.