-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Extend maintenance:repair to allow runtime repairs. #31995
Comments
GitMate.io thinks possibly related issues are #13281 (Repair step to clean up oc_properties), #14109 (apache should run without mod_dav), #25164 (Allow user specific maintenance mode), #31464 (File cache repair step detection should not run on every upgrade), and #30989 (Remove pagination from the repair step). |
My bad, maintenance mode is enabeld by this command: core/core/Command/Maintenance/Repair.php Line 101 in 6b521b4
|
Hmm, but this also means that the repair step will induce a maintenance mode and might surprise admins. We could either add a confirmation prompt or refuse to run if not in maintenance mode ? |
Added initial stuff here - got hung up adding tests around \OC\Repair which doesn't use DI and has static stuff. 25921a0 |
I agree, prefer to fail if maintenance mode is no enabled and prompt. Right now it just does it. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
Right now repair steps can be executed whilst in production withocc maintenance:repair
and relies on the individual repair step to protect itself from maintenance mode etc.We could extend the
maintenance:repair
command to have a--runtime
or--production
command to run only those that can run in production without maintenance mode, and protect all others with a maintenance mode check.cc @PVince81
The text was updated successfully, but these errors were encountered: