[
https://issues.apache.org/jira/browse/BROOKLYN-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928190#comment-15928190
]
ASF GitHub Bot commented on BROOKLYN-455:
-----------------------------------------
Github user aledsage commented on the issue:
https://github.com/apache/brooklyn-docs/pull/157
Thanks @drigodwin - I've added a bug report and fixed the link (to
https://issues.apache.org/jira/browse/BROOKLYN-455). Will merge this now.
> Web-console for inherited config uses wrong DSL evaluation context
> ------------------------------------------------------------------
>
> Key: BROOKLYN-455
> URL: https://issues.apache.org/jira/browse/BROOKLYN-455
> Project: Brooklyn
> Issue Type: Bug
> Reporter: Aled Sage
> Priority: Minor
>
> With 0.11.0-SNAPSHOT, I deployed the app shown below:
> {noformat}
> services:
> - type: org.apache.brooklyn.entity.stock.BasicApplication
> brooklyn.config:
> ownConfig: parentValue
> exampleConfig: '$brooklyn:config("ownConfig")'
> brooklyn.children:
> - type: org.apache.brooklyn.entity.stock.BasicEntity
> brooklyn.config:
> ownConfig: childValue
> refExampleConfig: '$brooklyn:config("exampleConfig")'
> {noformat}
> As expected, the {{refExampleConfig}} gets the "exampleConfig" value, which
> is a DSL evaluated in the context of the entity that declares it. It
> therefore has the value {{parentValue}}.
> However, the web-console's view of the child entity's config also shows the
> inherited config {{exampleConfig}}. It shows the value {{childValue}}, which
> I think is wrong -
> it has evaluated the {{$brooklyn:config("ownConfig")}} in the context of the
> child entity instead of the parent. As demonstrated by {{refExampleConfig}},
> it would have a different value if actually used.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
