Repository navigation
Conversation
Add revision-scoped migrations, workload revision gates, durable OGC aggregation recovery, configurable TimescaleDB policies, and upgrade documentation.
Disable Alembic migrations and incremental OGC aggregation by default. Operators must review the target database state, take any required backup, and enable both features explicitly during deployment.
This branch has not been deployed
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.
Summary
This PR integrates the Analytics database lifecycle into the shared geOrchestra Helm chart.
It complements georchestra/analytics#34 and follows the design described in GIP #25.
Changes
0001.2.30.2-pg18.2.2.0.Safe defaults
Database lifecycle operations are deliberately disabled by default:
Operators must review the target database, take any required backup and explicitly enable these features during deployment:
For the first deployment over an existing pre-Alembic installation:
The baseline command validates the expected schema before stamping it and does not move an already-versioned database backwards.
Validation
The chart was validated with:
helm lint;0003;The cross-repository lifecycle validation uses the Analytics application checkout to build the CLI image and this repository to deploy the shared chart. The complete workflow passed successfully.