[Bug]: Config is set to be read-only via option "config_is_read_only"

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

If the option config_is_read_only it's not possible to upgrade

Steps to reproduce

1. Set the option config_is_read_only in the Nextcloud config
2. Attempt to update Nextcloud

Expected behavior

If there is an option to be set in

Also, this makes it impossible to manage the Nextcloud config as code. I am currently hosting Nextcloud in Kubernetes and manging the config files as ConfigMaps.

If this is a forbidden deployment mode should be documented. Especially since there is a config option created that appears to be designed for this specific scenario.

Nextcloud Server version

30

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response

Start by reproducing the upgrade failure with config_is_read_only enabled, then trace where that option is handled during the update flow. Done means the intended upgrade behavior is established and implemented, or the restriction on ConfigMap-managed deployments is clearly documented.