Github user geomacy commented on the issue: https://github.com/apache/brooklyn-server/pull/338 Latest update - adds resource lookup from nested catalog definitions. Nested resources already have a test, [`testIndirectCatalogItemCanLoadResources`](https://github.com/geomacy/brooklyn-server/blob/master/camp/camp-brooklyn/src/test/java/org/apache/brooklyn/camp/brooklyn/catalog/CatalogYamlEntityTest.java#L919), which succeeds, however, this is because of the workaround @neykov mentions [here](https://github.com/geomacy/brooklyn-server/blob/master/camp/camp-brooklyn/src/test/java/org/apache/brooklyn/camp/brooklyn/catalog/CatalogYamlEntityTest.java#L952-L953). The latest couple of commits above first introduce a test, `testDeepCatalogItemCanLoadResources`, which illustrates that the workaround doesn't cover the more general case, and then updates the resource loading code to use the nested catalog item ids to load resources, which fixes the test.
--- 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. ---