OpenChoreo Developer GitOps Guide

Git is the source of truth; the cluster is its reflection. This skill writes OpenChoreo application resources to Git (Project / Component / Workload / ComponentRelease / ReleaseBinding), lets Flux reconcile them, and reads cluster state with occ to verify.

This skill is scoped to application-developer GitOps work. Repo scaffolding, Flux wiring, and authoring platform CRDs (ComponentTypes, Traits, Workflows, Environments, DeploymentPipelines, SecretReferences, AuthzRoles, planes) are out of scope — they're done by whoever owns the platform side. Don't edit GitOps-managed resources via occ apply -f or any other direct write path; Flux will revert them on the next reconcile.

Step 0 — Hard preconditions

Two checks; both must pass before proceeding.

# 0a — occ configured against the right cluster
command -v occ && occ config context list && occ namespace list

# 0b — cwd is inside a scaffolded GitOps repo
ls flux 2>/dev/null && ls platform-shared 2>/dev/null && ls namespaces 2>/dev/null

If occ is missing / unconfigured, point the user at https://openchoreo.dev/docs/getting-started/cli-installation.md and stop. If the cwd isn't a scaffolded repo (no flux/ or clusters/<name>/, platform-shared/, namespaces/), ask the user for the repo path; if no repo exists, tell them the repo needs scaffolding upstream of this skill — don't start creating components in a non-scaffolded directory.