Bug 971204 - REST API changes can potentially break clients, need to avoid changing an existing attribute
Summary: REST API changes can potentially break clients, need to avoid changing an exi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Master
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Lili Nader
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-06 01:56 UTC by Clayton Coleman
Modified: 2015-05-15 00:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-24 14:51:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Clayton Coleman 2013-06-06 01:56:22 UTC
Given that most requests to /broker/rest/api are not version qualified, we cannot change the type of the "versions" value from string to float.

We should introduce a new attribute "api_version" which is a float and leave "version" as a string (in API >= 1.5).

Blocks release

Comment 1 Jordan Liggitt 2013-06-07 16:09:16 UTC
Will our API version always be able to be expressed as a float? e.g. no more than one point version?

Comment 2 Clayton Coleman 2013-06-12 14:43:09 UTC
We cannot exit this sprint with this issue.

Comment 5 zhaozhanqi 2013-06-18 10:00:45 UTC
Tested this issue on devenv_3373, it has been fixed.


             <type>string</type>
              <description>The key portion of an rsa key (excluding ssh-rsa and comment)</description>
              <valid-options/>
              <invalid-options/>
            </param>
          </required-params>
          <optional-params/>
        </link>
      </links>
    </user>
  </data>
  <messages/>
  <version>1.5</version>
  <api-version>1.5</api-version>
  <supported-api-versions>
    <supported-api-version>1.0</supported-api-version>
    <supported-api-version>1.1</supported-api-version>
    <supported-api-version>1.2</supported-api-version>
    <supported-api-version>1.3</supported-api-version>
    <supported-api-version>1.4</supported-api-version>
    <supported-api-version>1.5</supported-api-version>
  </supported-api-versions>
</response>


Note You need to log in before you can comment on or make changes to this bug.