Remove lifecycle_type_backfill job - #5401
Open
WeiQuan0605 wants to merge 1 commit into
Open
Conversation
WeiQuan0605
force-pushed
the
deploy2-lifecycle-type-non-nullable
branch
2 times, most recently
from
August 27, 2026 10:59
eeba047 to
bf70f15
Compare
5 tasks
WeiQuan0605
force-pushed
the
deploy2-lifecycle-type-non-nullable
branch
from
August 27, 2026 12:30
bf70f15 to
8c11d34
Compare
WeiQuan0605
changed the title
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.
Related to #5067
A short explanation of the proposed change:
Removes the one-off
lifecycle_type_backfillclock job, its configuration,and related scheduler entries. This job was introduced in Deploy 1 to
backfill NULL lifecycle_type values and is no longer needed.
An explanation of the use cases your change solves
Cleans up the temporary backfill job once all installations have had
sufficient time to run it.
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