Univention Bugzilla – Bug 57316
The Appcenter should offer an option to specify if a "univention-app reinitialize" is supported
Last modified: 2024-05-23 17:25:08 CEST
univention-app offers the command "reinitialize", which throws away the container and starts a new one. With some apps this works well (I think e.g. nextcloud) but with others (e.g Keycloak) this will result in a broken, not-starting container. This results in support cases or even the support "breaking" a container by accident. Some apps depend heavily on their configure* scripts for the container to be functional. For example, Keycloak reads the LDAP for some of the Appsettings. This is done during the configure script. A "reinitialize" is done during the run of the configure script. Among other things Currently it is not clear if that reinitialize works for that specific app or not. I propose that the Appcenter should have some kind of option that doesn't allow a reinitialization. It should also make the error message configurable so that the App provider can enter what should be done instead. (E.g. in Keycloaks case: run univention-app configure). Additionally, univention-app reinitialize will need a "force" flag so that it can be used internally even if the app doesn't really support it.
I completely agree that this is a valid problem and something we should tackle, but to me this goes a bit too much into a solution proposal while the underlying issue might profit from something different. For me the question would be: Why does this happen in the first place, so why is the command called? We should find a solution that solves this use case and also prevents app breakage on the way. Was there a trigger for you to open the request, so someone I could talk to to understand the problem?