Issue 4092: Mark "FAILED" droplets/packages as expired #4093
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.
Droplets and packages in state "FAILED" shall be marked as "EXPIRED" so that they eventually get cleaned up. For packages, delete jobs shall only be created if there is a hash (= package has a blob).
An explanation of the use cases your change solves
Prevents accumulation of old package/droplet rows in the database.
Links to any other associated PRs
Droplets without a
droplet_hash
and in stateFAILED
are never cleaned up #4092I have reviewed the contributing guide
I have viewed, signed, and submitted the Contributor License Agreement
I have made this pull request to the
main
branchI have run all the unit tests using
bundle exec rake
I have run [CF Acceptance Tests] (https://github.com/cloudfoundry/cloud_controller_ng/blob/main/spec/README.md#cf-acceptance-tests-cats)
-> locally on a dev bbl env