We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-7432

Persist Optimize running mode as part of metadata

    • Icon: Task Task
    • Resolution: Duplicate
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • None
    • Not defined

      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

        This is the controller panel for Smart Panels app

            Loading...
            Uploaded image for project: 'Camunda Optimize'
            1. Camunda Optimize
            2. OPT-7432

            Persist Optimize running mode as part of metadata

              • Icon: Task Task
              • Resolution: Duplicate
              • Icon: L3 - Default L3 - Default
              • None
              • None
              • None
              • Not defined

                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

                  This is the controller panel for Smart Panels app

                        Unassigned Unassigned
                        joshua.windels Joshua Windels
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              Unassigned Unassigned
                              joshua.windels Joshua Windels
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              1 Start watching this issue

                                Created:
                                Updated:
                                Resolved: