Skip to content

fix(container): convert compose.yaml and .gatekeeper.yaml to KYAML - #12

Merged
hyperpolymath merged 1 commit into
mainfrom
fix/container-yaml-kyaml
Nov 14, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
fix/container-yaml-kyaml

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

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 requires build/container/compose.yaml, compose.example.yaml and build/container/stapeln/.gatekeeper.yaml to be KYAML. This repository's own compose.yaml and .gatekeeper.yaml were 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): --check on main says 2 of 2 files are not KYAML; compose.example.yaml is already KYAML. After this change --check passes 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 -I0 before 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

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
@coderabbitai

coderabbitai Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

You'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.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

Commits

Reviewing files that changed from the base of the PR and between 2897d27 and 92ce731.

Files selected for processing: 2

  • build/container/compose.yaml
  • build/container/stapeln/.gatekeeper.yaml

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.

Share

@sonarqubecloud

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath marked this pull request as ready for review November 14, 2026 17:50
@hyperpolymath
hyperpolymath merged commit d89403e into main Nov 14, 2026
42 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-14T17:51:55.951178Z 92ce731 Draft marked ready
🔒 Security Review ✅ Completed 2026-11-14T17:52:20.196319Z 92ce731 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants