Move mount.json to database configuration

[PVince81]

Part of #19156

• REQUIRES: occ command to add/edit/delete/import configs: Add occ command to add/change/delete ext storage configs #20368
• move mount.json to database by implementing a DB backend for the configuration
• provide migration path to move existing configs to the DB (at update time?)

@icewind1991 @DeepDiver1975

[PVince81]

Note: there was already some thinking done here #11261 (comment) regarding a possible DB structure.

CC @Xenopathic

[PVince81]

One challenge I see is for the mount.json in user homes, might require a repair step that iterates over all users. (please note that in many cases "userid" != "home folder name" in LDAP)

[karlitschek]

A way to add,edit,delete mountpoints via occ is needed before we can do that. This is critical to automate certain deployment scenarios.

[PVince81]

@karlitschek you're right, I forgot those details. Added in the original post and raised as #20368

[icewind1991]

WIP: #20370

[PVince81]

We already have comments to import/export configs, closing.
The other ones are part of the task for providing occ commands for more fine-grained ext storage management.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.