GitHub user grkvlt opened a pull request:
https://github.com/apache/brooklyn-server/pull/428
Adding new LocationEntity for creating location specific entities
A new type that allows configuring different entities depending on the
location being deployed to. Uses configuration like this:
```YAML
- type: org.apache.brooklyn.entity.stock.LocationEntity
brooklyn.config:
location.entity.spec.default:
$brooklyn:entitySpec:
type: traefik-load-balancer
location.entity.spec.aws-ec2:
$brooklyn:entitySpec:
type: elastic-load-balancer
location.entity.spec.gce:
$brooklyn:entitySpec:
type: google-load-balancer
```
The map entries can also be class names like `JcloudsLocation` or ISO 3166
country codes like `UK`.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/grkvlt/brooklyn-server location-entity
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/428.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 #428
----
commit 9943655ea24e29d25fd219bd899d2669b6ea88b9
Author: Andrew Donald Kennedy <andrew.kenn...@cloudsoftcorp.com>
Date: 2016-11-11T00:45:58Z
Adding new LocationEntity for creating location specific entities
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
