c73dc36a8c
## Description For accounts that were recovered post deletion (within x days), we were not removing the entry from data_cleanup cron. The data_clean up cron anyways verify that the account is indeed deleted before proceeding with deletion, so it was not causing any harm, but the cron was logging error. ## Tests - [x] Verify that data clean up entry is removed if the account is recovered - [x] Verify that for existing data_cleanup entry for already recovered account, the entry is deleted from cron. |
||
---|---|---|
.. | ||
authenticator | ||
cast | ||
datacleanup | ||
embedding | ||
kex | ||
passkey | ||
remotestore | ||
storagebonus | ||
two_factor_recovery | ||
userentity | ||
billing.go | ||
collection.go | ||
family.go | ||
file.go | ||
file_size.go | ||
notificationhistory.go | ||
object.go | ||
object_cleanup.go | ||
object_copies.go | ||
public_collection.go | ||
push.go | ||
queue.go | ||
srp.go | ||
tasklock.go | ||
trash.go | ||
twofactor.go | ||
usage.go | ||
user.go | ||
userauth.go |