nextcloud / nextcloud/server

Limit commands outside of maintenance hours

Open
#31,101 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement feature: occ
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
There are occ commands which are very disruptive and can even create downtimes for minutes and hours.

Describe the solution you'd like
Since #30945 a "maintenance window" can be configured.

When a disruptive command is being executed outside of the maintenance hours we should highlight that and ask for a quick confirmation first.

The following commands come to mind:

  • app:update
  • db:add-missing-columns
  • db:add-missing-indices
  • db:add-missing-primary-keys
  • db:convert-filecache-bigint
  • db:convert-mysql-charset
  • db:convert-type
  • encryption:decrypt-all
  • encryption:encrypt-all
  • maintenance:repair --include-expensive

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the maintenance-window configuration introduced in #30945 and the listed OCC commands: app:update, the database conversion commands, encryption commands, and maintenance:repair --include-expensive. Done means disruptive commands warn when run outside configured maintenance hours and require quick confirmation before proceeding.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend, cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.