Mailing-List: contact dev-help@brooklyn.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.incubator.apache.org
From: ahgittin <git@git.apache.org>
To: dev@brooklyn.incubator.apache.org
Reply-To: dev@brooklyn.incubator.apache.org
Message-ID: <git-pr-595-incubator-brooklyn@git.apache.org>
Subject: [GitHub] incubator-brooklyn pull request: Make YAML more powerful
Content-Type: text/plain
Date: Mon, 13 Apr 2015 01:02:28 +0000 (UTC)

GitHub user ahgittin opened a pull request:

    https://github.com/apache/incubator-brooklyn/pull/595

    Make YAML more powerful

    allowing a `firstMemberSpec` for cluster, make enrichers easier to set up in yaml (with good example), and better support for referring to sensors within maps (esp when configuring enrichers)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ahgittin/incubator-brooklyn yaml-more-powerful

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-brooklyn/pull/595.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 #595
    
----
commit 64b19928d80bef311f3f1dfebfa075466aad82c7
Author: Alex Heneveld <alex.heneveld@cloudsoftcorp.com>
Date:   2015-04-02T11:23:47Z

    add an optional config `firstMemberSpec` to DynamicCluster, with test

commit 8591999ff24555cf798c590b27b31f4da5368c87
Author: Alex Heneveld <alex.heneveld@cloudsoftcorp.com>
Date:   2015-04-10T11:24:54Z

    enhance yaml DSL for specifying a sensor
    
    allows `sensor("sensor.name")`, looking up on entity, falling back to untyped Object sensor

commit bf66d3ec9e8c9423b7552650f5168fb5af9245a1
Author: Alex Heneveld <alex.heneveld@cloudsoftcorp.com>
Date:   2015-04-10T11:31:16Z

    tidy yaml ref docs

commit 18b6529f557794c8ff180b19bdd4937f01c8efcb
Author: Alex Heneveld <alex.heneveld@cloudsoftcorp.com>
Date:   2015-04-12T16:51:44Z

    map config key improvements
    
    * resolve deep on extraction
    * do not coerce/resolve on setting
    * subkey extraction looks in parent map
    * keys in maps put in the config map will be resolved when the map is gotten (but subkeys will not match suppliers as keys)

commit f7142a3333fdabdbec0e6eb606e7b595fd8491ef
Author: Alex Heneveld <alex.heneveld@cloudsoftcorp.com>
Date:   2015-04-13T00:56:16Z

    make enrichers easier to configure from yaml
    
    * entity spec keeps the list of specs, for things like enrichers, because equality (set duplication) is not very good for specs
    * makes many of the basic enrichers easier to configure from yaml, with more flexible config
    * in particular `Transformer` can be given a value supplier, e.g. `$brooklyn:formatString`
    * adds a `Joiner` enricher which does `Strings.join`, handy for converting a list to something which can be used in bash
    * good example of all of these in test-app-with-enrichers-slightly-simpler.yaml, referenced in the docs reference page

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---