Description Felix Botner 2021-07-23 15:37:03 CEST

+++ This bug was initially created as a clone of Bug #52506 +++

The apps Jitsi and Bitwarden use App Settings with the outside scope and store the values in UCR variables. Furthermore, both apps use an environment file which is a UCR template referring to UCR variables that are created by the app settings.

The problem is that app settings are evaluated after the Docker containers are created and started. The environment file is not yet updated and therefore the containers are initialized with the wrong values.

The workaround for the problem is to add the following if block to the `configure_host` lifecycle script in the app:

if [ "$1" = "install" ]; then
    univention-app reinitialize $appid
fi

This causes the the re-evaluation of the app settings and the UCR templates like compose and environment file for the app during the installation process. The containers are thrown away and recreated with the correct settings. The UCR variables are still configured from the initial installation run. Afterwards, the join script is run.

The order of certain tasks during the installation process needs to be reviewed. As administrator and app provider I expect that app settings made before installation are correctly applied to the Docker containers regardless of the App Settings' scope. UCR template files like the app's Docker compose and the environment file also need to be taken into account.