Github user ahgittin commented on the issue:
https://github.com/apache/brooklyn-server/pull/748
@neykov I've never liked the split between catalog metadata and item
definition. Given that we have it currently, it doesn't feel like a bad dev
practise to disallow their separation during dev.
If we could remove the split we could make the BOM YAML simpler and remove
the need for the two paths. That would mean putting catalog metadata into the
definition, IE baking fields such as `id`, `description`, and `icon_url` into
the definitions -- and I guess being able to ignore them if given to the type
instantiation and that ignores them. But that feels messier than having the
split?
---
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.
---
