[
https://issues.apache.org/jira/browse/BROOKLYN-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634128#comment-16634128
]
ASF GitHub Bot commented on BROOKLYN-602:
-----------------------------------------
GitHub user aledsage opened a pull request:
https://github.com/apache/brooklyn-server/pull/1004
BROOKLYN-602: fix config key order for yaml overrides
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aledsage/brooklyn-server fix-BROOKYLN-602
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/1004.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 #1004
----
commit 1a410be58602d063161fdf746c7aa048b6da9be5
Author: Aled Sage <aled.sage@...>
Date: 2018-10-01T14:49:20Z
BROOKLYN-602: fix config key order for yaml overrides
----
> priority of parameters should not be reset by extending a config key in yaml
> ----------------------------------------------------------------------------
>
> Key: BROOKLYN-602
> URL: https://issues.apache.org/jira/browse/BROOKLYN-602
> Project: Brooklyn
> Issue Type: Bug
> Affects Versions: 1.0.0-M1
> Reporter: Aled Sage
> Priority: Minor
>
> Currently, if you write a yaml entity that extends an entity to add
> constraints / descriptions to the config keys, it re-orders the keys: the
> keys declared in the yaml appear at the top.
> The order should be preserved.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
