Add measured Depot Registry pull-through canary - #1156
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
📝 WalkthroughWalkthroughThis change adds a manually triggered Depot Registry pull-through canary. It validates pinned images, compares upstream and Depot pull times across fresh runners, verifies digests, summarizes threshold eligibility, and documents CI trust and measurement requirements. ChangesDepot Registry pull-through canary
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant GitHubActions
participant UpstreamRegistry
participant DepotRegistry
participant PullSummarizer
GitHubActions->>GitHubActions: Validate exact-main dispatch and digest-pinned image
GitHubActions->>UpstreamRegistry: Pull image and record elapsed time
GitHubActions->>DepotRegistry: Obtain OIDC token and pull mirror image
GitHubActions->>GitHubActions: Verify manifest digest and upload observations
GitHubActions->>PullSummarizer: Generate JSON and Markdown threshold reports
Possibly related PRs
Suggested reviewers: ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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 |
Summary
Validation
python3 -m unittest scripts.tests.test_depot_registry_canary_workflow scripts.tests.test_summarize_depot_registry_pullsactionlint .github/workflows/depot-registry-canary.ymlgit diff --checkPull-through caching remains disabled in normal builds until each mapping passes the canary.
Summary by CodeRabbit
New Features
Documentation
Tests