Replies: 1 comment
-
Yeah I think the right approach here is to externalize the transformation in (for example) a Kafka application that listens for the event, fetches the details from Registry, then performs the transformation and publishes a new event. The purpose of the event source feature is to externalize integration logic as much as possible. Supporting custom transformations within Registry would run counter to that goal/design. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This is probably out of scope of this application but would be really nice to have. Let's say we are working with openapi definitions. Now when there is a change (create/update) of openapi, we would like to retrieve some data from within openapi (paths, servers) using some transformation function and then send those data within event which is already published e.g.
ArtifactCreated
. Would there be a chance to register some transformation function which could then include those data inside event?Benefit is that if we already have all related data (openapi + some transformation) we don't have to do postprocessing in some different application. So one roundtrip of reading data from apicurio registry is saved.
We are trying to build automated gateway which will configure routes/security based on openapi...something similar to this https://github.com/Apicurio/api-controller/tree/main
Beta Was this translation helpful? Give feedback.
All reactions