Repository navigation
fix(container): convert compose.yaml and .gatekeeper.yaml to KYAML - #12
Conversation
The template upgrade (#8) brought in the KYAML ratchet in estate-rules.yml ("Converted YAML stays KYAML"), which lists build/container/compose.yaml, compose.example.yaml and build/container/stapeln/.gatekeeper.yaml. This repository's own compose.yaml and .gatekeeper.yaml were still block-style YAML, so the ratchet fails on them (kyaml-format.sh --check: 2 of 2 not KYAML). Both files go through the pinned formatter (standards f0b3cd4 kyaml-format.sh, mikefarah yq 4.53.3, the checksums CI verifies). Names are unchanged, since the tools read these filenames. The parsed data is identical before and after (yq to JSON, byte-for-byte), and the comment count is unchanged (30 and 59). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7Zm6f3TYUpUuzGd5KAQ
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 9 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
|
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |



Root cause of the KYAML red the sweep saw on #8. The template upgrade (#8, now merged) brought in the template's KYAML ratchet ("Converted YAML stays KYAML" in
estate-rules.yml), which requiresbuild/container/compose.yaml,compose.example.yamlandbuild/container/stapeln/.gatekeeper.yamlto be KYAML. This repository's owncompose.yamland.gatekeeper.yamlwere block-style YAML, identical to main and not touched by #8. So the content is wrong (case A), not the gate: the gate is the template's, and sholes main's own estate-rules now runs it too.Reproduced locally with the same pinned tools CI installs (standards f0b3cd4
kyaml-format.sh, mikefarah yq 4.53.3, both SHA-256 verified):--checkon main says 2 of 2 files are not KYAML;compose.example.yamlis already KYAML. After this change--checkpasses on all three.What changed: the two files go through the pinned formatter, nothing else. Names are unchanged (tool-demanded). Evidence the data is unchanged:
yq -o=json -I0before and after compare byte-for-byte identical for both files, and the comment count is unchanged (30 and 59). Not claimed: CI and Sonar on this head, which are unread.Generated by Claude Code