Skip to content

Dashboard

The Dashboard is your main workspace for viewing, editing, and applying configuration across your units. This guide walks through a common task: updating a value using the Function Browser and applying the change to your cluster.

What You'll Do

  • Open the Dashboard for a unit
  • Use the Function Browser to update a config value (e.g. namespace)
  • Preview the diff and apply the change

Opening the Dashboard

Navigate the dashboard in the tools section of the ConfigHub app navigation. The dashboard opens to the Overview tab, showing current sync status, recent activity and additional information on the status of your units.

Unit Dashboard Overview

Editing Config with the Function Browser

The Function Browser lets you update config values without writing raw YAML. It surfaces the functions available for the selected unit(s) toolchain type(s).

  1. Select the unit(s) you want to edit in the left unit navigation.
  2. Open the Function Browser panel on the right side.

  3. Select the function you want to modify — for example, set-namespace.

    Note

    Hover over any function in the list to see its details — including the name, description, and parameters — without opening it.

  4. Update the input value (e.g. change confighubplaceholder → your-namespace).

  5. The editor reflects the change in the rendered output immediately.

Note

You can also edit values directly in the YAML editor if you prefer — both approaches produce the same result. The Function Browser is recommended for structured inputs since it validates values against the function's schema.

Applying the Change

Once saved, the unit will show as out of sync or not live if it hasn't been applied to the cluster yet — the config has changed but the cluster hasn't been updated yet.

  1. From the dashboard there will be a floating contextual menu, click Apply.
  2. ConfigHub sends the updated manifests to the worker, which applies them to the cluster.
  3. The dashboard updates to show the apply result — synced targets turn green.

What Happened

  • ConfigHub creates a queued operation and marks it as pending.
  • The worker — which maintains a persistent stream connection to the server — picks it up almost immediately.
  • The worker then renders your unit's config into final manifests and applies them to the cluster using the target's toolchain (e.g. kubectl apply for Kubernetes/YAML, a sync trigger for ArgoCD).
  • Once the cluster confirms the result, the worker posts the outcome back to ConfigHub.
  • The server then updates the unit's live revision to match the head, writes an event to the audit trail, and — if other units depend on this one — triggers their resolve cycle so downstream config stays in sync.

Tip: Monitor applies from the Dashboard Overview

The Dashboard Overview (visible when no single unit is selected) gives you a live view across all your units. The stat cards at the top filter by state — click In Progress to watch active applies, or Unapplied Changes to see what's queued. The Latest Events feed and Sync Activity Heatmap show outcomes in real time as applies complete. Quickly view apply gates including units awaiting approvals before syncing updated manifests to the cluster.

Next Steps

  • Promotion — flow config changes from dev → staging → prod
  • GitOps Import — bring existing ArgoCD apps into ConfigHub