Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.apache.org
From: alasdairhodge <git@git.apache.org>
To: dev@brooklyn.incubator.apache.org
Reply-To: dev@brooklyn.incubator.apache.org
References: <git-pr-1172-incubator-brooklyn@git.apache.org>
In-Reply-To: <git-pr-1172-incubator-brooklyn@git.apache.org>
Subject: [GitHub] incubator-brooklyn pull request: Adds catalog item example
 to exte...
Content-Type: text/plain
Message-Id: <20160122151008.5B001E0098@git1-us-west.apache.org>
Date: Fri, 22 Jan 2016 15:10:08 +0000 (UTC)

Github user alasdairhodge commented on a diff in the pull request:

    https://github.com/apache/incubator-brooklyn/pull/1172#discussion_r50546773
  
    --- Diff: brooklyn-docs/guide/ops/externalized-configuration.md ---
    @@ -122,6 +122,19 @@ brooklyn.location.jclouds.aws-ec2.credential=$brooklyn:external("mysupplier", "a
     {% endhighlight %}
     
     
    +## Referring to External Configuration in catalog items
    +
    +The same blueprint language DSL can be used within YAML catalog items. For example:
    +
    +    brooklyn.catalog:
    +      id: com.example.myblueprint
    +      version: 1.2.3
    +      brooklyn.libraries:
    +      - $brooklyn:external("mysupplier", "my-blueprint-lib")
    +      item:
    +        type: com.example.MyBlueprint
    +
    +
    --- End diff --
    
    Good thing to demonstrate,but example feels a bit contrived. Perhaps show a *location* catalog item, with user ID and credential externalised?


---
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.
---