[JBoss JIRA] (JBIDE-14744) Allow users to choose from quickstarts/templates when creatingApplication wizard: new application
3:27 p.m.
[
https://issues.jboss.org/browse/JBIDE-14744?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-14744 at 2/13/14 4:25 PM:
-------------------------------------------------------------------
So if there's no change in this, the only solution for us is to drop the distinction
when one selects a quickstart. This means for us that we have to offer an alternative 2nd
wizard page where quickstart cartridges are displayed or maybe edited (if there are
alternatives).
In a chat with clayton:
{quote}
(08:31:28 PM) clayton: adietish: so with a quickstart... why are you letting users choose
other things?
(08:31:37 PM) clayton: quickstart is intended to be "what you see is what you
get"
(08:31:41 PM) clayton: only specs should give users options
(08:31:56 PM) adietish: clayton: dont want to let users choose at free will.
(08:32:08 PM) clayton: adietish: what i'm asking is why let them choose anything
except specs
(08:32:14 PM) adietish: clayton: would simply love to re-use what we already have, what is
known to the users so far
(08:32:26 PM) clayton: adietish: i don't know if thaat's the right model for
quickstarts
(08:32:32 PM) clayton: a qucisktart with a downloadable url is saying "use
this"
(08:32:36 PM) adietish: clayton: We're not planning to let users pick at free will
(08:33:12 PM) adietish: clayton: so display alternatives in combos...
(08:33:19 PM) adietish: clayton: could work, like in web-ui
(08:33:58 PM) adietish: clayton: but would have to drop the distinction web-/addon-cart
like we have in "free config"
(08:34:05 PM) clayton: adietish: yeah i'd strongly recommend assuming that the
quickstart author knows what they're doing
(08:34:06 PM) adietish: clayton: sounds doable
(08:34:14 PM) clayton: if a user wants to tweak afterwards that's an option
(08:34:19 PM) clayton: i'm not opposed to something better in quickstarts
(08:34:32 PM) clayton: but what i was hoping is that we'd wait until the oo-index
stuff develops to make changes
{quote}
oo-index is a standalone index of quickstarts: https://github.com/openshift/oo-index
the broker is currently not delivering this but has its own custom-made listing.
was (Author: adietish):
So if there's no change in this, the only solution for us is to drop the
distinction when one selects a quickstart. This means for us that we have to offer an
alternative 2nd wizard page where quickstart cartridges are displayed or maybe edited (if
there are alternatives).
In a chat with clayton:
{quote}
(08:31:28 PM) clayton: adietish: so with a quickstart... why are you letting users choose
other things?
(08:31:37 PM) clayton: quickstart is intended to be "what you see is what you
get"
(08:31:41 PM) clayton: only specs should give users options
(08:31:56 PM) adietish: clayton: dont want to let users choose at free will.
(08:32:08 PM) clayton: adietish: what i'm asking is why let them choose anything
except specs
(08:32:14 PM) adietish: clayton: would simply love to re-use what we already have, what is
known to the users so far
(08:32:26 PM) clayton: adietish: i don't know if thaat's the right model for
quickstarts
(08:32:32 PM) clayton: a qucisktart with a downloadable url is saying "use
this"
(08:32:36 PM) adietish: clayton: We're not planning to let users pick at free will
(08:33:12 PM) adietish: clayton: so display alternatives in combos...
(08:33:19 PM) adietish: clayton: could work, like in web-ui
(08:33:58 PM) adietish: clayton: but would have to drop the distinction web-/addon-cart
like we have in "free config"
(08:34:05 PM) clayton: adietish: yeah i'd strongly recommend assuming that the
quickstart author knows what they're doing
(08:34:06 PM) adietish: clayton: sounds doable
(08:34:14 PM) clayton: if a user wants to tweak afterwards that's an option
(08:34:19 PM) clayton: i'm not opposed to something better in quickstarts
(08:34:32 PM) clayton: but what i was hoping is that we'd wait until the oo-index
stuff develops to make changes
{quote}
Allow users to choose from quickstarts/templates when
creatingApplication wizard: new application
-------------------------------------------------------------------------------------------------
Key: JBIDE-14744
URL: https://issues.jboss.org/browse/JBIDE-14744
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.1.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Labels: application_wizard
Fix For: 4.2.0.Beta1
Attachments: 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml,
2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22
17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.png,
alternative-cartridges.png, crobson_2014-01-28 16.11.bmml, crobson_2014-01-28 16.11.bmml,
crobson_2014-01-28 16.11.png, openshift-quickstart.png
The web ui offers a large set of quickstarts/templates:
!openshift-quickstart.png!
in a mail from clayton on the 4th of june:
{quote}
For QuickStarts, brokers may choose to
a) enable community quickstarts
(the URL you saw below, set by COMMUNITY_QUICKSTART_URL being a URL in
/etc/openshift/broker.conf)
b) enable their own list of quickstarts
(a different url, /broker/rest/quickstarts, configured from
/etc/openshift/quickstarts.json)
c) disable the quickstarts link
(delete /etc/openshift/quickstarts.json)
To correctly fetch the quickstarts for a server, retrieve the API document
/broker/rest/api
and look for the LIST_QUICKSTARTS link. If it is present, you may retrieve quickstarts.
If it is absent, you should assume there are no quickstarts.
Retrieving the list of quickstarts, unlike other REST API feed calls, is very specific:
* API versioning is not supported
* Only JSON is supported
* The body of the response is slightly different than standard REST API feed results
* If you encounter a parse error or an unexpected data value you are required to handle
it gracefully by omitting the entry - the API may change without warning (although
hopefully not)
The format of the JSON response (in either a) or b) above) is:
{quote}
{code}
{
data: [
quickstart: {
id: "<string id>",
href: "<absolute URL to a display URL for the quickstart>",
name: "<name>",
updated: "<last update date in seconds from the epoch>",
summary: "<brief HTML body of the item>",
body: "<full HTML body of the item>",
cartridges: "<cartridge spec>",
website: "<URL of metadata about the source of the quickstart or the
technology>",
tags: "<comma delimited list of tags>",
language: "<display name of the type of quickstart>",
initial_git_url: "<absolute URL or Git reference to source>",
provider: "openshift|reviewed|partner|community", # default is community
},
]
}
{code}
{quote}
You should assume that arbitrary content could be injected into any of these fields and
defend yourself against XSS appropriately. You should also assume that the structure
could be changed at any time.
Cartridge spec:
The cartridge spec is defined as either:
a) a comma delimited list of cartridge name search conditions
b) a string containing a JSON array
If the leading character of the cartridge spec is '[', you must convert the
cartridge spec to JSON and submit the value provided to the server on creation as the
"cartridges" field.
Otherwise,
1) split the string by "," into "segments"
2) trim whitespace from each segment
3) split each segment by "|" into "matches" - these represent logical
ORs
4) strip leading and trailing "*" characters
5) For each segment, return all cartridges that have a case-insensitive substring match
on any of the "matches" in that segment for the user to select.
See
https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea...
and
https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea...
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4545
days inactive
4545
days old
jbosstools-issues@lists.jboss.org
0 comments
1 participants
participants (1)
-
Andre Dietisheim (JIRA)