GitHub user geomacy opened a pull request:

    https://github.com/apache/brooklyn-server/pull/781

    Support DSL in template options

    At the moment it's not possible to specify DSL in template options - for 
example you can't do 
    
          - type: some-type-publishing-subnet-id
            id: ent1
    
          - type: some-service
            id: service
            brooklyn.config:
              provisioning.properties:
                templateOptions:
                  subnetId: 
$brooklyn:entity("ent1").attributeWhenReady("subnet.id")
    
    see new test 
[here](https://github.com/geomacy/brooklyn-server/commit/d2f5bf9e0a5038208ff98aedb16795c217d01fc7#diff-99cb6184bb386646b61f6678346ec63bR75).
    
    This adds support in `TemplateOptionsOption` for evaluating options that 
are tasks (I would have used more explicit DSL related classes but for a 
circular dependency that would create between `camp-brooklyn` and 
`brooklyn-locations-jclouds`.   This allows the approach in the blueprint above 
to be used.

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

    $ git pull https://github.com/geomacy/brooklyn-server 
support-dsl-in-template-options

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

    https://github.com/apache/brooklyn-server/pull/781.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 #781
    
----
commit d2f5bf9e0a5038208ff98aedb16795c217d01fc7
Author: Geoff Macartney <[email protected]>
Date:   2017-07-27T16:08:29Z

    Add test for DSL in template options.

commit 660a784adfebf20a1058c57e4e56458716102727
Author: Geoff Macartney <[email protected]>
Date:   2017-07-27T16:08:55Z

    Support DSL in template options in provisioning properties

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to