You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@brooklyn.apache.org by "Aled Sage (JIRA)" <ji...@apache.org> on 2018/10/01 14:46:00 UTC

[jira] [Created] (BROOKLYN-602) priority of parameters should not be reset by extending a config key in yaml

Aled Sage created BROOKLYN-602:
----------------------------------

             Summary: 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


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)