Skip to content

Conversation

@jfroche
Copy link
Collaborator

@jfroche jfroche commented Dec 1, 2025

Implement content-based caching for stage 1 AMI builds by computing a hash from all input sources. Then the build-ami script checks for existing AMIs with matching input hash before building.

@jfroche jfroche force-pushed the ci/cache-stage1 branch 11 times, most recently from 6a14659 to fae40c8 Compare December 3, 2025 01:14
@jfroche jfroche marked this pull request as ready for review December 3, 2025 11:13
@jfroche jfroche requested review from a team as code owners December 3, 2025 11:13
@samrose samrose force-pushed the ci/cache-stage1 branch 2 times, most recently from 23cd71a to 793d9d9 Compare December 4, 2025 11:54
@jfroche jfroche force-pushed the ci/cache-stage1 branch 4 times, most recently from c870e16 to 9524496 Compare December 4, 2025 16:06
jfroche and others added 6 commits December 4, 2025 17:58
Implement content-based caching for stage 1 AMI builds by computing a hash from all input sources.
Then the build-ami script checks for existing AMIs with matching input hash before building.
… add actionlint

Consolidate duplicate AMI build steps across workflows into a shared
composite action. Also introduces actionlint configuration for GitHub
Actions validation for the modified workflows.
@jfroche jfroche force-pushed the ci/cache-stage1 branch 2 times, most recently from 0c2e1d9 to 0b25bbd Compare December 5, 2025 19:17
In order to differentiate AMIs built for testing and those built for
release, we need different AMI name. This commit introduces a new input
parameter `ami_name_prefix`. For test builds, we set this prefix to
include the GitHub run ID, ensuring uniqueness across test builds. For
release builds, we use a static prefix "supabase-postgres".
The force-deregister variable is not used in the stage2-nix-psql.pkr.hcl
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