Uploaded image for project: 'Marathon'
  1. Marathon
  2. MARATHON-7635

Introduce schema versioning to support easier migration to 1.5 API

    Details

      Description

      Marathon 1.5 has introduced an API that normalizes legacy input, but produces incompatible output, thus breaking consumers of the v2 API. We are concerned that this will prevent users from upgrading, and have already faced several issues where components were forced to adjust.

      As a first means to mitigate problems for components that need to talk to both 1.4 instances and 1.5 instances and don't know to which one they are talking, we'll add a schema version that allows consumers to identify version they have to deal with.

      TODO: create Sub-tasks after scoping:

      • add the version to all responses from 1.5 on
      • clarify what the version is (1.5.x? An incremental integer? v2? ...?)
      • clarify the format of how to put the version into the responses (a String? An object containing major/minor/patch?)
      • clarify how we put the version into the response (Header value? An additional field in the body? If body: how do we treat this with plain text responses?)

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                matthias.eichstedt Matthias Eichstedt
                Reporter:
                matthias.eichstedt Matthias Eichstedt
                Team:
                Orchestration Team
                Watchers:
                Adam Bordelon (Inactive), Matthias Eichstedt
              • Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: