apicurio-registry
apicurio-registry copied to clipboard
Cross OpenAPI schema validation and processing
Feature or Problem Description
I'm investigating if Apicurio can have capabilities across multiple artifacts.
For example, I have Service A and Service B. Each has different lifecycles and are updated separately.
I would like to have a way to:
- Validate both OpenAPI (check if paths aren't overriding each other)
- Produce Gateway Schema based on the Service A and Service B
- Based on the updates on Service A and Service B I would like to produce a new gateway schema.
So far I do not see any way to do this apart from building another layer on top of Apicurio (catching pre and post-operations on Apicurio). Am I missing anything?
Proposed Solution
Additional Context
Thank you for reporting an issue!
Pinging @carlesarnal to respond or triage.
You aren't missing anything - we don't have anything like what you've described. It sounds pretty specific to a gateway product use-case, where you're creating a mashup of multiple services.