335942408679d281a5809cd7f56d2253ce3caa1e
The step embedded multi-line Python at column zero — a heredoc terminator in one repo, an inline -c script in the other — and both dedented straight out of the run: block scalar, so the workflow did not parse as YAML at all and the job it belongs to could never start. It is one indented line now. The lookup is unchanged: read the ApplicationSet, find the source whose chart is app, print its repository and target revision. A missing source raises instead of returning nothing, which is the point of parsing the document rather than grepping it — the comment above already said a silent miss renders against whatever the registry calls latest.
Zoo Universe — retired
Read-only from here. Canonical: https://git.hanzo.ai/zoo/universe
This tip is an ancestor of canonical main, so no commit reachable from this
branch is unique to it — the canonical repo is a strict superset. Nothing was
lost by stopping here.
Two universes for one org is a split brain: a push lands somewhere real, reports
success, and never reaches a cluster, because CD reconciles the other one
(deploy/applicationset.yaml names the canonical URL). One repo per org means
that failure cannot happen.
Description
Declared state for the zoo fleet: one values file per service, one ApplicationSet
1.2 MiB
Languages
TypeScript
70.1%
Shell
21.5%
Makefile
8.4%