lburgazzoli commented on issue #1818: URL: https://github.com/apache/camel-k/issues/1818#issuecomment-730883524
> @oscerd Why not? Isn't it just a place to put stuff? The examples I saw are basically just yaml or json documents. Take a look here: [apicur.io/registry/docs/apicurio-registry/1.3.2.Final/assets-attachments/registry-rest-api.htm](https://www.apicur.io/registry/docs/apicurio-registry/1.3.2.Final/assets-attachments/registry-rest-api.htm) It goves you an idea of the data model. > > At the moment the registry doesn't have any notion of Kamelets, but it could I guess. There are some interesting traits: > > * validation > > * rules that govern modifcations > > * versioning > > * metadata > > > I think all of these could be interesting to a registry that manages kamelets. I think it would technically be possible and as you mentioned it would offer some nice things like version and validation, however I wonder if it would be semantically correct as a kamelet defines both the signature (with a json schema and the schema for in/out data) as well as the implementation of the API itself. FWIW, I think we have or at least we thought about having an option to use the registry to store the schemas associated to the kamelet. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
