Details
-
Task
-
Resolution: Duplicate
-
L3 - Default
-
None
-
None
-
None
-
Not defined
Description
We don't currently persist which mode (platform, cloud, ccsm) a given installation of Optimize is running in, rather determining that by the Spring profile at startup. Once Optimize has started in a given mode, there is no support for it changing mode. We should therefore consider storing this profile in the DB for later access, to support cases where determining the profile is not possible/easy.
This problem is especially important during operations outside of normal runtime, such as upgrades and reimport.
Notes:
- We could probably write it to the metadata index at first startup, and this field should never be updateable
- Bonus: Starting Optimize in a different mode to that stored in the metadata index could even be rejected with a helpful exception
