Repository navigation
fix(github): isolate bootstrap readiness from application delivery - #4472
Conversation
Validation at
CI is rerunning. This is validation evidence, not a readiness verdict or a claim that deployment has completed. |
@coderabbitai review |
✅ Action performedReview finished.
|
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. 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 59 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (13)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (8)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📜 Recent review details🧰 Additional context used🧠 Learnings (1)📚 Learning: 2026-08-10T13:01:12.782ZApplied to files:
🔇 Additional comments (8)
📝 WalkthroughWalkthroughThe GitHub Config Flux Kustomization now sets Priority: ⬆️ High Severity of issue fixed: High Merge Risk: ⚪ Minimal · up to GitHub repository bootstrap should no longer hold up unrelated application delivery, while the existing health check and validation remain in place. No identified issue blocks merging. Security Architecture ReviewSecurity architecture risk: 🔵 Low · up to The change isolates GitHub setup failures without intentionally widening access or removing application-health checks. The remaining uncertainty is whether independent reconciliation and alerting preserve failure visibility during degraded operation and recovery. Retained concerns Security review detailsSecurity Blast Radius
Trust Boundaries and Controls
Resilience and Maintainability Implications
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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. Comment |
Ready at User evaluation exercised the actual production render and guard, confirmed the parent application-health gate stays enabled, and reproduced a pending GitHub managed resource through the existing Crossplane alert fixture. Enabling wait or adding explicit child health checks fails the new regression; missing, duplicate or malformed input remains UNKNOWN. Pending resources remain visible to monitoring. Authorization conservation and its real pinned-renderer check are recorded in #4472 (comment). Promoting the exact reviewed head. Production convergence and the latest protected-base deployment remain merge-queue gates, followed by live readback. |
The first protected deployment was rejected by the Flux reliability admission policy because the GitHub bootstrap resource now intentionally uses asynchronous reconciliation. The PR remains draft while that mismatch is repaired; it has not been blindly requeued. The policy repair permits the asynchronous setting only for the exact platform-owned GitHub configuration identity and retains interval, timeout, retry, pruning, and source requirements. New admission fixtures fail against the old policy and pass after the repair. They also reject a matching name in another namespace, another name in the same namespace, a parent application health bypass, and disabled pruning. All 385 Kyverno assertions pass, and the fixture-evaluation guard confirms every declared row was evaluated. The bootstrap guard, its negative and incomplete-census controls, the full authorization suite, and the actual rendered authorization check pass. Current-head CI and review remain required before another protected deployment attempt. |
…thub-bootstrap-isolation-2626-round15
devantler
left a comment
There was a problem hiding this comment.
🤖 Generated by the Agentic Engineer
Self-review (fallback — CodeRabbit, Codex and Cursor Bugbot unavailable)
Reviewed commit: fff15dc
- CodeRabbit: the account-wide included-review rate-limit refusal was observed at 2026-10-04T17:13:45Z on devantler-tech/agent-plugins#473 (comment) and remains inside its stated 28-minute reset window. The prior CodeRabbit green artifact covers only the superseded 64bffd4 head and is not reused.
- Codex: the account-wide usage-limit refusal was observed at 2026-10-04T02:11:02Z on devantler-tech/ksail#7433 (comment) and requires account credits or settings recovery.
- Cursor Bugbot: the user/team usage-limit refusal was observed at 2026-10-04T12:21:20Z on devantler-tech/ksail#7481 (comment) and requires usage or spend recovery.
- Direct current-PR review objects, comments, threads, and checks were read before this fallback. The complete thread census is empty and no provider finding is being discarded.
- The complete diff was reviewed for exact-identity policy scoping, retained Flux reliability controls, GitHub bootstrap isolation, Crossplane alert continuity, deployment guard ordering, authorization conservation, and fail-closed fixture coverage.
- Exact-head validation passed all 385 Kyverno assertions, all 32 fixture-evaluation censuses, the bootstrap guard and its negative/incomplete controls, and the authorization suite with checksum-verified kubectl v1.36.2 / Kustomize v5.8.1. The installed v1.37.1 renderer was independently confirmed to fail closed.
Verdict: no P0/P1 findings
…p-isolation-2626-round15
devantler
left a comment
There was a problem hiding this comment.
🤖 Generated by the Agentic Engineer
Exact-head local review at 8ce09f198b7911ece25aa11be094d6df298dd69b: no P0/P1 findings. Re-reviewed the refreshed diff after merging current main; the exact github-config/github-config identity exception retains interval, timeout, retry, prune and source constraints, lookalikes remain denied, and the parent applications layer remains health-gated. Exact-head verification passed the bootstrap guard, ShellCheck, all 385 Kyverno cases, and 308 EKS policy-validator tests.
@coderabbitai review |
|
devantler
left a comment
There was a problem hiding this comment.
🤖 Generated by the Agentic Engineer
Self-review (fallback, exact head)
Reviewed commit: 8ce09f198b7911ece25aa11be094d6df298dd69b
- CodeRabbit: LIMITED — review-lane health observed a rate-limit at 2026-10-04T18:35:13Z, retry after 2026-10-04T19:25:10Z.
- Codex: DOWN — account-wide usage limit remains active; maintainer-only recovery.
- Cursor Bugbot: DOWN — account-wide usage limit observed at 2026-10-04T18:18:31Z; maintainer-only recovery.
Re-reviewed the refreshed diff after merging current main. The exact github-config/github-config exception retains interval, timeout, retry, prune, and source constraints; identity lookalikes remain denied; the parent applications layer remains health-gated. Exact-head evidence: all 25 hosted checks passed (8 expected skips), the bootstrap guard and ShellCheck passed, all 385 Kyverno cases passed, and all 308 EKS policy-validator tests passed.
Verdict: no P0/P1 findings
Exact-head readiness at |
Actual protected merge verified: #4472 merged at 2026-10-04 18:59:58 UTC as Scoped live readback confirms the GitHub reconciliation is Ready with No incident or alert was manually resolved, and no credential or access boundary was changed. |
Why
A GitHub repository waiting for manual setup can currently block every application deployment. Organisation housekeeping should remain visible without freezing unrelated delivery.
What
Let GitHub resources reconcile independently while retaining deployment errors and alerts for unsynced resources. Add a required check to prevent the delivery coupling from returning.
Fixes #2626