Bug 1319997

Summary:	Increase REST functionality to match that of oc binary
Product:	OpenShift Container Platform	Reporter:	Jaspreet Kaur <jkaur>
Component:	RFE	Assignee:	Michal Fojtik <mfojtik>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Johnny Liu <jialiu>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.1.0	CC:	aos-bugs, bparees, dave.mccormick, erich, jkaur, jokerman, mmccomas, sspeiche
Target Milestone:	---
Target Release:	3.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-12 16:20:48 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:

Description Jaspreet Kaur 2016-03-22 05:48:11 UTC

1. Proposed title of this feature request
Increase REST functionality to match that of oc binary

3. What is the nature and description of the request?
I would like the RESTful interface to have endpoints that perform actions matching those of the oc binary,

e.g. creating an application from template

“oc new-app mytemplate –e PARAM=value”

4. Why does the customer need this? (List the business requirements here)

It is not practical to provide and update the oc binary to every user. Would be much more useful if every user could just use curl to use the same functionality

5. How would the customer like to achieve this? (List the functional requirements here)
An additional separate REST endpoint which contains functions e.g. POST /oc/newapp/template

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Run oc functions, then run their RESTful equivalents and ensure the results are identical

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No

8. Does the customer have any specific timeline dependencies and which release would they like to target ?
ASAP

9. Is the sales team involved in this request and do they have any additional input? Red Hat Consultant on site, account team fully aware of the request.
No

10. List any affected packages or components.

11. Would the customer be able to assist in testing this functionality if implemented?
Yes

Comment 2 Ben Parees 2016-04-13 13:57:22 UTC

I think this RFE is asking for an api endpoint where you can POST a template object and have that template get instantiated.  Or where you can POST to an endpoint using the name of a registered/installed template to instantiate that template.

That contrasts with today's template endpoints which return a processed template and then the client must iterate the objects in the template and create each one via an explicit api call.

Can someone confirm?

Comment 3 Dave McCormick 2016-04-22 09:34:48 UTC

Yes this is what we want

Comment 4 Jaspreet Kaur 2016-08-05 08:56:58 UTC

Hello Ben,

Customer confirmed on #2 and they are actually looking for this.

Regards,
Jaspreet

Comment 5 Steve Speicher 2016-08-16 17:44:28 UTC

At this point it is unlikely that we'll support this, as it would require us to adopt a pattern we haven't done with running multiple commands in one REST call (process the template, get list of resources, create each resource, handle errors).

We are continuing to investigate options.

Comment 12 Steve Speicher 2017-12-12 16:20:48 UTC

I'm considering this closed as the primary request is to have a template API which we delivered in 3.7. There is other work for a Go client (coming in 3.9) that can be tracked here: https://trello.com/c/PTDrY0GF.

Please open specific RFEs for functionality missing in REST api.