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

Allow maxAge config as either String or number

    XMLWordPrintable

Details

    • Task
    • Resolution: Unresolved
    • L3 - Default
    • None
    • 3.10.0, 3.10.1, 3.9.5, 3.10.2, 3.10.3, 3.10.4, 3.10.5
    • backend
    • Not defined

    Description

      Context:

      With OPT-6724 we mistakenly changed the htst max age config to a string instead of a number. Users for whom this caused a casting error implemented a workaround to define their config max age as a string. If possible we would like to allow users to set max age either as a string (of a number) or a number in their config so no further changes are needed on their end.

      AT:

      • max age config setting can be set as a string of a number or a number
      • if max age is set as a string with non numeral characters (eg "text" instead of "123"), an error is logged accordingly

      Testing Notes:

      • Start Optimize with max age set to a number, Optimize should start as expected and no config errors should occur
      • Start Optimize with max age set to a string of a number (eg "1"), Optimize should start as expected and no config errors should occur
      • Start Optimize with max age set to a string of a non numeric content (eg "text"), Optimize should log an error that this field is misconfigured

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Activity

            People

              Unassigned Unassigned
              helene.waechtler Helene Waechtler
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Salesforce