Github user geomacy commented on the issue:
https://github.com/apache/brooklyn-server/pull/562
ð lgtm, merging
---
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
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/562
Good point about casts, updated.
---
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
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/562
@geomacy Addressed comments, can you take another look.
---
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
Github user tbouron commented on the issue:
https://github.com/apache/brooklyn-server/pull/562
@neykov Agree, having this warning within the docs seems to be the way to
go.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user neykov commented on the issue:
https://github.com/apache/brooklyn-server/pull/562
Good idea about a limited interface @geomacy. If you look at the change
sites you'll find out that a `context` is hard to identify. On the other hand
using a `ConfigKey` for the key gives
