-
Notifications
You must be signed in to change notification settings - Fork 87
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
Fix expire commands and background job when trash and/or version apps are disabled #1849
Conversation
/backport to stable23 |
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.
Overall this looks good to me, but I'm not familiar enough with the codebase to provide a thorough review at the moment. It would be good if someone could do a bit of testing with the different cases (trash & versions disabled, trash enabled, versions enabled, trash & versions enabled).
9940ac5
to
49a3e10
Compare
… are disabled Signed-off-by: Carl Schwan <[email protected]>
49a3e10
to
bc21eee
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.
Make sure you test before merge.
Tested with the 4 combinations and everything work! |
Fix #1815
Fix #1812
For the background jobs, split the version expiration and trash expiration in two separate jobs. Both use the same placeholder in case the respective app is not enabled.
For the commands, create 4 different versions (using inheritance) with the 4 different combo enabled/disabled.
Signed-off-by: Carl Schwan [email protected]