[
https://issues.apache.org/jira/browse/BROOKLYN-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976923#comment-15976923
]
ASF GitHub Bot commented on BROOKLYN-482:
-----------------------------------------
GitHub user aledsage opened a pull request:
https://github.com/apache/brooklyn-server/pull/642
BROOKLYN-482: yaml config key default vals immutable
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aledsage/brooklyn-server BROOKLYN-482
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/642.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 #642
----
commit 15da8e50aa4cb8618da3948cbefa614c50877bc5
Author: Aled Sage <[email protected]>
Date: 2017-04-20T15:34:50Z
BROOKLYN-482: yaml config key default vals immutable
----
> Config Key default value (in yaml) of type List is mutable
> ----------------------------------------------------------
>
> Key: BROOKLYN-482
> URL: https://issues.apache.org/jira/browse/BROOKLYN-482
> Project: Brooklyn
> Issue Type: Bug
> Reporter: Aled Sage
> Priority: Minor
>
> In version 0.11.0-rc2...
> As described in https://github.com/apache/brooklyn-docs/pull/172, it's
> important that config key default values are immutable.
> However, in a yaml catalog item or blueprint if you declare a config key of
> type {{java.util.List}} (or Set, Collection or Map) with {{[]}} then that is
> mutable.
> For example:
> {noformat}
> brooklyn.catalog:
> itemType: entity
> items:
> - id: entity-with-keys
> item:
> type: server
> brooklyn.parameters:
> - name: my.list.key
> type: java.util.List
> default: ["myDefaultVal"]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
