Github user ahgittin commented on the issue:
https://github.com/apache/brooklyn-server/pull/648
As I wrote on mailing list:
```
I'd like to keep backwards compatibility. We don't know where this might
be used.
Also the catalog item ID isn't sufficient I don't think. Returning just
the catalog item ID means you lose any custom configuration on the location in
the blueprint (ie on top of the catalog item ID); I'm not sure it even works at
all if you use legacy "jclouds:aws-ec2" syntax; and you won't get any
added-after-deployed information. It isn't a problem in many cases but it is a
weaker API.
Could we add a new "locationsDetail" field which contains eg "{ [ id: <old
value>, catalogItemId: <what you want>, displayName: <optional>, ... ] }" and
we could add any further metadata we want?
I'd also be in favour of doing this for all entities, not just applications.
```
---
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.
---
