Add lifecycle_type backfill clock job#5196
Open
philippthun wants to merge 1 commit into
Open
Conversation
A one-off clock job that backfills the lifecycle_type column on apps, droplets, and builds for rows that pre-date the column's introduction. Once all installations have run it long enough to drain those rows, this job will be removed. The job processes up to 1000 (BATCH_SIZE) * 10 (BATCHES_PER_RUN) rows per table in short transactions, idempotent and bounded. It is defensive against missing columns: schema(:table) is checked on each invocation, so it would be safe to be shipped together with the migration that introduces the column.
philippthun
force-pushed
the
lifecycle-type-backfill
branch
from
088537d to
a16ae37
Compare
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
1 participant
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.
A one-off clock job that backfills the
lifecycle_typecolumn on apps, droplets, and builds for rows that pre-date the column's introduction. Once all installations have run it long enough to drain those rows, this job will be removed.The job processes up to 1000 (
BATCH_SIZE) * 10 (BATCHES_PER_RUN) rows per table in short transactions, idempotent and bounded. It is defensive against missing columns:schema(:table)is checked on each invocation, so it would be safe to be shipped together with the migration that introduces the column.I have reviewed the contributing guide
I have viewed, signed, and submitted the Contributor License Agreement
I have made this pull request to the
mainbranchI have run all the unit tests using
bundle exec rakeI have run CF Acceptance Tests