Github user ahgittin commented on the issue:
https://github.com/apache/brooklyn-server/pull/300
@neykov yes referencing the `MachineLocation` is probably what people want
right now but conceptually it is a hack to hard code that. i think we should
**not** hack things into the `$` DSL: they will be hard to undo.
i'd prefer to look at building out the DSL around *relations* and use that.
eg a jquery-ish
`$brooklyn:relation("RUNNING_ON_MACHINE_LOCATION").wait("30s").requireUnique().config("host.address")`.
in the interim what about the simple approach of a policy that publishes
the `MachineLocation` as a sensor and the DSL allowing
`attributeWhenReady("my.machine").config("spec.final")` ?
---
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.
---
