brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Heneveld (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BROOKLYN-329) $brooklyn:config hangs, rather than getting default brooklyn.parameter value
Date Fri, 09 Dec 2016 12:52:58 GMT

    [ https://issues.apache.org/jira/browse/BROOKLYN-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15735236#comment-15735236
] 

Alex Heneveld commented on BROOKLYN-329:
----------------------------------------

hard to read GitHub's posts so to summarise

#462 fixes items (1), (5), and (6) above
#480 fixes (2) and (3+4)

immediate evaluation continues not to require new threads except in a few cases (and notes
on eliminating/improving that have been added)

believe this issue can be closed when those PR's are merged

> $brooklyn:config hangs, rather than getting default brooklyn.parameter value
> ----------------------------------------------------------------------------
>
>                 Key: BROOKLYN-329
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-329
>             Project: Brooklyn
>          Issue Type: Bug
>            Reporter: Aled Sage
>            Priority: Minor
>
> Using 0.10.0-SNAPSHOT...
> I wrote a YAML entity where CouchDB was configured with an initial username/password,
and another app that included CouchDB would inject it.
> In each blueprint, I defined a brooklyn.parameter with a default value for the username/password.
I used the same config key name in each.
> However, when I ran my blueprint it hung. The CouchDB was waiting forever for the username/password
config value.
> I recreated this behaviour in the simpler test case below (which I'll add to {{ConfigParametersYamlTest}}).
> The workaround is to use a different name for the config key in each blueprint. For example,
in the outer blueprint above if youchange the name to {{my.param.key2}} then the test passes.
> Debugging it, one surprising thing I noticed is that {{scopeRoot()}} evaluates to be
"entity-with-tests" rather than {{wrapper-entity}}.
> {noformat}
> public void testConfigParameterPassedFromOuterConfigParameter() throws Exception {
>     addCatalogItems(
>             "brooklyn.catalog:",
>             "  itemType: entity",
>             "  items:",
>             "  - id: entity-with-keys",
>             "    item:",
>             "      type: "+TestEntity.class.getName(),
>             "      brooklyn.parameters:",
>             "      - name: my.param.key",
>             "        type: string",
>             "        default: myDefaultVal",
>             "      brooklyn.config:",
>             "        my.other.key: $brooklyn:config(\"my.param.key\")");
>     addCatalogItems(
>             "brooklyn.catalog:",
>             "  itemType: entity",
>             "  items:",
>             "  - id: wrapper-entity",
>             "    item:",
>             "      brooklyn.parameters:",
>             "      - name: my.param.key",
>             "        type: string",
>             "        default: myDefaultValInOuter",
>             "      type: entity-with-keys",
>             "      brooklyn.config:",
>             "        my.param.key: $brooklyn:scopeRoot().config(\"my.param.key\")");
>     
>     String yaml = Joiner.on("\n").join(
>             "services:",
>             "- type: wrapper-entity");
>     
>     Entity app = createStartWaitAndLogApplication(yaml);
>     final TestEntity entity = (TestEntity) Iterables.getOnlyElement(app.getChildren());
>     Asserts.assertReturnsEventually(new Runnable() {
>         public void run() {
>             assertEquals(entity.config().get(ConfigKeys.newStringConfigKey("my.other.key")),
"myDefaultValInOuter");
>         }},
>         Asserts.DEFAULT_LONG_TIMEOUT);
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message