[jbosstools-issues] [JBoss JIRA] (JBDS-3306) Create Deployment from Template

Jeff Cantrill (JIRA) issues at jboss.org
Fri Jun 5 09:05:03 EDT 2015


    [ https://issues.jboss.org/browse/JBDS-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13074670#comment-13074670 ] 

Jeff Cantrill commented on JBDS-3306:
-------------------------------------

[~burrsutter] [~maxandersen] As coded now, you can basically do this flow with the exception of step "i".  A user must explicitly import the new app.  Post summit, we will add the import into the new app flow

> Create Deployment from Template
> -------------------------------
>
>                 Key: JBDS-3306
>                 URL: https://issues.jboss.org/browse/JBDS-3306
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>          Components: openshift, requirements
>            Reporter: Burr Sutter
>            Assignee: Jeff Cantrill
>            Priority: Blocker
>             Fix For: 9.0.0.Beta1
>
>
> Use Case #3
> Create Deployment from Template
> a) Assume OpenShift is started remotely and provides an entrypoint URL
> b) Assume end-user is logged in (ignore auth for now)
> c) Eclipse user will open a dialog and enter the URL from step a
> d) Eclipse user will then be presented with a list of templates from the template library
> (initially a set of files on the local filesystem until openshift has a real template library api) 
> e) The template list should allow sorting so that higher priority items are at the top
> We will likely need some form of categorization for templates also
> f) The template list should be searchable by keyword 
> g) Eclipse user will select a particular template and
> h) Create a new openshift deployment based on selected template
> i) follow steps JBDS-3297 f through j (clone, import, project facets, etc)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


More information about the jbosstools-issues mailing list