Proposal: Include a common package for the brokers that allows them access to user provided schema definitions . The user can provide the broker with a path to a folder containing CRD's (local or public/internet I.E one could point to https://github.com/triggermesh/triggermesh/tree/48061197f7bacc33477a6576752eeac45978ffee/config) and the package will illiterate over all of the files to look for a `registry.knative.dev/eventTypes` parameter . From here the package can make the following information available to the Broker: The event type, schema definition, and a small description. With the broker now equipped with this information we can begin to leverage it by: * Autogenerate swagger endpoint * Event type validation. * Payload validation. * Auto Transformation / AI transformation
Proposal: Include a common package for the brokers that allows them access to user provided schema definitions .
The user can provide the broker with a path to a folder containing CRD's (local or public/internet I.E one could point to https://github.com/triggermesh/triggermesh/tree/48061197f7bacc33477a6576752eeac45978ffee/config) and the package will illiterate over all of the files to look for a
registry.knative.dev/eventTypesparameter .From here the package can make the following information available to the Broker: The event type, schema definition, and a small description.
With the broker now equipped with this information we can begin to leverage it by: