feat: clean up ami build so that nix closures handle installs - #2402
Draft
encima wants to merge 2 commits into
Draft
feat: clean up ami build so that nix closures handle installs#2402encima wants to merge 2 commits into
encima wants to merge 2 commits into
Conversation
PostgreSQL Extension Dependency Analysis: PR #2402
SummaryNo extensions had dependencies with MAJOR version updates. Full Analysis ResultsPostgreSQL 15 Extension DependenciesPostgreSQL 17 Extension DependenciesOrioleDB 17 Extension Dependencies |
PostgreSQL Package Dependency Analysis: PR #2402
SummaryNo packages had MAJOR version updates. Full Analysis ResultsPostgreSQL 15 Dependency ChangesExtracting PostgreSQL 15 dependencies...
Runtime Closure Size
Raw Dependency ClosurePostgreSQL 17 Dependency ChangesExtracting PostgreSQL 17 dependencies...
Runtime Closure Size
Raw Dependency Closure |
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
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.
What kind of change does this PR introduce?
Feature: part of CE-76 (https://linear.app/supabase/issue/CE-76/investigate-an-additional-snapshot-volume-option-for-postgres-upgrades)
What is the current behavior?
AMI is the source of truth for all builds
What is the new behavior?
AMI is built without being tagged to a git commit. We now build the AMI but we can handle installs via nix closures so that individual components can be updated via nix (using Salt)
Additional context
This is purely early exploration into assisting with speeding up build times and selfishly improving the upgrade process so that automated minor downtime upgrades are easier to implement