Skip to content

Configuration Loader

The Configuration Loader is the service that ingests .kiket definition repositories and translates them into runtime objects. It keeps workspaces in sync with Git while surfacing validation errors quickly.

Sync Triggers

  • Webhooks – Push notifications from GitHub/GitLab trigger incremental syncs.
  • CLI – kiket config sync forces a sync (useful during development).
  • Scheduled jobs – Nightly sweeps catch missed webhooks or branches.

Processing Stages

  1. Fetch – Clone or download the definition repo at the requested revision.
  2. Scan – Detect files by namespace (workflows/, boards/, projects/, etc.).
  3. Validate – Run schema checks and compatibility rules per file.
  4. Load – Persist validated definitions to the workspace.
  5. Publish – Notify subscribers (UI, CLI, command palette) that a new revision is active.

Error Handling

  • Errors are written to ProjectConfigurationSyncLog records with timestamps and file pointers.
  • The UI highlights failing sections so authors can jump directly to the offending file.
  • CLI users see summarized tables plus the raw log via kiket config sync --verbose.

Best Practices

  • Keep repos small and focused (one workspace per repo when possible).
  • Use feature branches to test risky workflow or analytics changes.
  • Add automated tests or linters in CI that run kiket config validate.

With the loader in place, teams can treat workflow and analytics updates the same way they manage application code.