Backup API returns separate error code for ES connection errors

XMLWordPrintable

    • Type: Task
    • Resolution: Fixed
    • Priority: L3 - Default
    • 3.10.0-alpha2, 3.10.0
    • Affects Version/s: None
    • Component/s: backend
    • None

      Context:

      If customers have automated error handling for use of the backup API, it would be useful to have a separate error code in case we cannot connect to Elasticsearch. As discussed with zeebe and operate, we will return a 502 in that case.

       

      AT:

      • all backup endpoints return a 502 if there is a ES connection error
      • confluence docs are updated
      • user docs are updated

       

      Testing Notes:

      • Confirm Optimize returns a 502 when calling any of the backup API endpoints while connection to Elasticsearch is compromised

       

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Helene Waechtler
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: