Add draft supabox manifest-diff workflow - #2447
Draft
brainrake wants to merge 6 commits into
Draft
Conversation
Calls supabox's tag:manifest suite (supabase/supabox#216) once per ref, diffing the resulting rootfs. MPG-117 / RFC: declarative system management. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
e2e.yml's Blacksmith sticky disk is keyed by profiles+latest only (supabase/supabox#214), not by repo pin, so same-flavor parallel builds race on the same cache. Chain pr after baseline. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
e2e.yml's own concurrency group is per-run_id for workflow_call, so two PRs' calls race independently on the same profile-keyed sticky disk. A workflow-level group serializes across PRs instead. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Replaces the supabox-based approach: snapshot rides the same session-scoped instance testinfra_ami_nix.py already boots per PR, zero extra AMI builds. Develop-side S3 caching is blocked pending a region/instance-profile decision for us-east-1 (see PR description). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Bare instance launch (temp SG + EC2 Instance Connect), same pattern Packer already uses in this account/region. Uploads to S3 as the develop baseline for the AMI manifest diff. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Manifest snapshot for the AMI, no supabox needed:
testinfra/test_ami_nix.py(viatestinfra-ami-build.yml), zero extra EC2 cost. Uploaded as a build artifact.ami-release-nix.yml(amd64 leg) launches a bare, temporary instance from the just-built AMI in us-east-1 (temp security group + EC2 Instance Connect, same pattern Packer itself already uses in this account/region), snapshots it, uploads to S3 as thelatest.txtbaseline.Part of MPG-117, the "RFC: declarative system management".
Known caveat: the PR-side instance's cloud-init runs a full staging project bootstrap before the manifest captures state, which can introduce per-boot noise (generated certs/keys) unrelated to actual AMI drift. Accepted for now.
🤖 Generated with Claude Code