Consider clearing `app_install_overwrite` (or warning about it when detected) for major version upgrades

[joshtrichards]

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.

Previously force enabled apps are tracked and kept as forced through major Nextcloud Server version upgrades, triggering mysterious post-upgrade problems. This results in Help Forum posts + invalid bug reports here.

Describe the solution you'd like

We clear the app_install_overwrite parameter before major Nextcloud Server upgrades (or) we warn heavily when that config directive is in-place.

Describe alternatives you've considered

• Manually clearing
• Better documenting
• Adding a check to warn/refuse to bump to a new major Nextcloud version if apps are force enabled (unless the Server upgrade itself is forced)

Additional context

• See the Help Forum and closed bug reports.
• I'm not certain there aren't some trade-offs if we clear this parameter; need to look closer
• https://github.com/nextcloud/server/pull/29988#issuecomment-1022732428

[szaimen]

Consider clearing app_install_overwrite

This is what AIO already does since quite a while: https://github.com/nextcloud/all-in-one/blob/b17561d41e575c7efd45fac1a6fb410be79bbe37/Containers/nextcloud/entrypoint.sh#L171-L173

[joshtrichards]

This is what AIO already does since quite a while

Nice. I hadn't realized that. So AIO gives us some real-world field experience with the proposed behavior change. Even better! :-)