Hi Lukas Lieb
Thank you for your response.
Our project has a custom app.yaml
in the project source. Then the script will apply that custom app.yaml
by copy it into configuration/applications/luz/
. So, our script will overwrite the app.yaml
of the migration process by the custom app.yaml
. Now I understand how we lost the global variables from the database. It was caused by our script.
We lost the global variables for some environments but we still need to do the upgrade for more important environments. So, we are finding a way to avoid this issue for our remaining environments.
You said:
Deployed app.yaml files are copied to the /applications/<app-name>/config/ folder and have a lower priority than configurations of the app.yaml in the configuration/applications/<app-name>/ folder. This means the variables from the SystemDB will "overwrite" deployed variables.
Let's call:
- Configuration from
/configuration/applications/<app-name>/
= main configuration.
- Configuration from
/applications/<app-name>/config/
= custom configuration.
=> Does it mean that if we change our script to copy our app.yaml
from the project source to /applications/<app-name>/config/
, both main and custom configurations will be applied with the higher priority for main configurations?