[ 
https://issues.apache.org/jira/browse/BROOKLYN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15958898#comment-15958898
 ] 

ASF GitHub Bot commented on BROOKLYN-460:
-----------------------------------------

GitHub user bostko opened a pull request:

    https://github.com/apache/brooklyn-docs/pull/162

    BROOKLYN-460: Brooklyn Camp syntax guidance

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bostko/brooklyn-docs yaml-tags

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/brooklyn-docs/pull/162.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #162
    
----
commit c24e01c4097e516f973c8203094fca0289ad54e2
Author: Valentin Aitken <[email protected]>
Date:   2017-04-06T13:08:55Z

    BROOKLYN-460: Brooklyn Camp syntax guidance

----


> Brooklyn Camp syntax for adding tags to an entity spec
> ------------------------------------------------------
>
>                 Key: BROOKLYN-460
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-460
>             Project: Brooklyn
>          Issue Type: New Feature
>            Reporter: Valentin Aitken
>            Priority: Minor
>             Fix For: 0.11.0
>
>
> Current requirement is to be able to supply String tags in an entity spec in 
> YAML so it can be then retrieved via REST API with {{GET 
> /v1/applications/<appId>/entities/<entityId>/tags}}.
> Example usage in a YAML blueprint:
> {noformat}
> services:
> - type: org.apache.brooklyn.entity.software.base.VanillaSoftwareProcess
>   brooklyn.tags:
>   - tag1
>   - tag2
> {noformat}
> Please shout if you have further requirements for {{brooklyn.tags}}.



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

Reply via email to