Uploaded image for project: 'OpenShift Java Client'
  1. OpenShift Java Client
  2. OSJC-12

support protocol version 1.2 in openshift-java-client

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 2.2.0
    • None
    • None

    Description

      The protocol for the OpenShift REST service has evolved over time and currently has v1.3. The rest service currently delivers 1.0, 1.1, 1.2 and 1.3.
      OpenShift Enterprise talks 1.2 and we therefore want to drop everything below it

      2012-03-14 in #libra

      07:08:20 PM) clayton: then adietish that's your answer - you're good to drop 1.1 and 1.0 support because we have no supported products in the field that use those api versions

      Attachments

        Issue Links

          blocks

          Sub-task - The sub-task of the issue OSJC-13 handle IApplication#getEmbeddedCartridges correctly with changes to protocol 1.2

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users OSJC-58 openshift-java-client: provide nice names, versions and descriptions for cartridges

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Feature Request - Feature requests from customers and/or users JBDS-2563 JBDS70_1213: [Commit] (?) (P?) Support Hosted OpenShift - Multiple "versions"

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users OSJC-52 use new openshift-java-client library with protocol 1.2 in JBT

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-14588 Create OpenShift Application from remote repository

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) OSJC-23 openshift-java-client: add support for initial git url when creating a new application

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) OSJC-47 openshift-java-client: provide nice descriptions for standalone and embeddable cartridges

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) OSJC-56 openshift java client: remove various API elements (show ports etc.)

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users OSJC-67 openshift-java-client: support multiple protocol version

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Activity

            People

              adietish@redhat.com André Dietisheim
              adietish@redhat.com André Dietisheim
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: