Github user grkvlt commented on the pull request:
https://github.com/apache/incubator-brooklyn/pull/322#issuecomment-62817934
Yes, exactly. We can have a separate Catalog repository for YAML plus
metadata. But we should also leverage other repositories as remote locations,
such as Artifactory, Bintray, GitHub and so on, as well as arbitrary HTTP
servers. And Brooklyn is essentially agnostic, just wanting an HTTP (or
whatever protocol) URL, or people can copy YAML themselves and pass it in
locally. If the metadata for a set of well known catalogs are published
somewhere then Brooklyn can scan those at startup, or use a configured list of
Catalog endpoints. Not sure about file extension, but agree `.yaml` is not
always specific enough to determine blueprint-ness of a file.
---
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.
---
