-
Notifications
You must be signed in to change notification settings - Fork 291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
blobuploadcleanupworker: Add BLOBUPLOAD_DELETION_DATE_THRESHOLD (PROJQUAY-2915) #1022
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -15,7 +15,7 @@ | |||
|
|||
logger = logging.getLogger(__name__) | |||
|
|||
DELETION_DATE_THRESHOLD = timedelta(days=2) | |||
DELETION_DATE_THRESHOLD = timedelta(hours=12) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we make this configurable instead. Something like BLOB_UPLOAD_DELETION_DATE_THRESHOLD
.
This way we can keep the current value as default, but allow it to be shorter or longer for others.
Not too dissimilar to how BLOBUPLOAD_CLEANUP_FREQUENCY
is being set.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added
…QUAY-2915) Added BLOBUPLOAD_DELETION_DATE_THRESHOLD option to configure TTL on orphaned blobs.
e396e4e
to
8bd5c17
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…QUAY-2915) (quay#1022) Added BLOBUPLOAD_DELETION_DATE_THRESHOLD option to configure TTL on orphaned blobs.
…QUAY-2915) (#1022) (#1023) Added BLOBUPLOAD_DELETION_DATE_THRESHOLD option to configure TTL on orphaned blobs.
Added the BLOBUPLOAD_DELETION_DATE_THRESHOLD internal property to configure the TTL on orphaned blobs.