Add scheduled clean up of old bookings#34
Merged
Conversation
nihas101
force-pushed
the
feat/delete-old-bookings
branch
from
July 11, 2026 10:33
cb3952b to
3a5f1ee
Compare
nihas101
marked this pull request as ready for review
July 11, 2026 10:33
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.
This MR adds a scheduled cleanup of 10 year old bookings to the service.
The job is executed with a delay of 1 hour and by default deletes a maximum of 1000 bookings per run before the cutoff (10 years).
This behavior can be customized with the following application properties:
midas.cleanup.enabled: Whether a cleanup of old bookings is triggered on startup of the applicationmidas.cleanup.cutoff: The period after which a booking is considered 'old' and eligible for cleanupmidas.cleanup.delayBetweenCleanups: Defines the duration between separate cleanup runmidas.cleanup.limit: The maximum number of bookings deleted during the cleanup phase. Setting this to-1disables the limit completely.Closes #31