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

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0.0-M1
• Fix Version/s: 1.0.0
• Assignee: Aled Sage
• Reporter: Aled Sage
• Created: 01/Oct/18 14:45
• Updated: 02/Oct/18 08:25
• Resolved: 02/Oct/18 08:25

Description

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.

Issue Links

• links to: GitHub Pull Request #1004