Bug 1111604

Summary: Json for Quickstarts delivered by Online differs from Enterprise
Product: OpenShift Online Reporter: Andre Dietisheim <adietish>
Component: MasterAssignee: Sally <somalley>
Status: CLOSED NOTABUG QA Contact: weiwei jiang <wjiang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.xCC: adietish, aos-bugs, bparees, jokerman, mmccomas, somalley, tiwillia, wsun
Target Milestone: ---Keywords: UpcomingRelease
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-07 20:50:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andre Dietisheim 2014-06-20 13:54:04 UTC
Description of problem:
The (format of the) json for quickstarts that you get from OpenShift Online differs from what you get from OpenShift Enterprise. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. get the listing of quickstarts in OpenShift Online
2. get the listing of quickstarts from OpenShift Enterprise (ex. console.itos.redhat.com)
3. compare the json

Actual results:
Ex. CakePHP quickstart:
* cartridges spec (json string with comma delimited items vs json array of strings):
1) OpenShift Online: 
<snip>
"cartridges": "php-, mysql-",
</snip>
2) OpenShift Enterprise (console.itos.redhat.com): 
<snip>
"cartridges" => [
        "php-5.3",
        "mysql-5.1"
    ],
</snip>
* tags (json string with comma delimited items vs json array of strings)
1) OpenShift Online: 
<snip>
"tags": "framework, instant_app, php",
</snip>
2) OpenShift Enterprise (console.itos.redhat.com): 
<snip>
"tags" => [
        "php",
        "cakephp",
        "framework"
    ],
</snip>

Expected results:
json and spec should ideally be identical

Additional info:

Comment 1 Andre Dietisheim 2014-06-20 23:20:27 UTC
I updated openshift-java-client in https://issues.jboss.org/browse/OSJC-118 and https://issues.jboss.org/browse/OSJC-114 to support the json arrays that OSE is delivering for tags, admin-tags and cartriges (instead of comma delimited items in a string as in OpenShift Online). 
Nevertheless these differences in json are suboptimal and cause more work in openshift-java-client with no added benefit consumer-wise. To openshift-java-client (and its users JBDS, Zend-Studion, jenkins-plugin, etc.) it is crucial to have an API that openshift-java-client can rely to. Ideally OSE and OpenShift Online would have identical json responses. Even more crucial is to catch whatever difference there is and solve it (either in OSE or openshift-java-client) before JBDS goes GA in July 2014.

Comment 2 Sally 2016-01-07 20:20:14 UTC
 These (now?) have the same format, I believe this bug is resolved.
 
 https://console.itos.redhat.com/broker/rest/quickstarts.json
 https://openshift.redhat.com/broker/rest/quickstarts.json