brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BROOKLYN-177) Support for drag and drop when editing Blueprints
Date Mon, 05 Oct 2015 06:49:26 GMT


ASF GitHub Bot commented on BROOKLYN-177:

Github user neykov commented on the pull request:
    * The text which comes from the REST API is valid YAML, not JSON (JSON is a subset of
YAML). You can do 
    var bp = jsyaml.load("services: [{ type: org.apache.brooklyn.entity.brooklynnode.BrooklynEntityMirror
    which will spit out:
    - type: org.apache.brooklyn.entity.brooklynnode.BrooklynEntityMirror
    Both of them are YAML, the latter one being idiomatic. But the `yamlPlan` is not useful
in this case because:
    * The `yamlPlan` of catalog items is the plan used to create the item, not example usage.
Try dropping `1-server-template:0.9.0-SNAPSHOT` from the default catalog for example to see
what I mean. What should be dropped instead is how the item is to be used, which is just the
`symbolicName:version` pair.
    Having the config keys as part of the pasted data is a good idea, but this is not available
from the REST API. It can still be obtained though, for example [the catalog docs](
extract the information offline, using the CLI item-lister command.

> Support for drag and drop when editing Blueprints
> -------------------------------------------------
>                 Key: BROOKLYN-177
>                 URL:
>             Project: Brooklyn
>          Issue Type: New Feature
>    Affects Versions: 0.8.0
>            Reporter: Alex Zbarcea
> Applications in Brooklyn are built via composing services. As services are available
in the catalog, yaml could be constructed much faster if a drag'n'drop feature would be available
allowing a user to select and drop the required entities. Further editing of the yaml would
still be necessary, but such a feature would also provide basic guidance to the user.

This message was sent by Atlassian JIRA

View raw message