An API artifact store retains processed API definitions so later pipeline stages, developer portals, SDK generators, and external consumers can retrieve the same publishable artifact. The pipeline stores the transformed definition separately from multifile source definitions and application executables. section 9.1 section 9.1.1
A build pipeline can prepare and publish the artifact through these steps:
- Bundle multifile OpenAPI definitions into one file. section 9.1
- Filter internal endpoints marked with x-internal, remove unused components, and sort fields consistently. section 9.1
- Lint the resulting definition before making it available for publication or downstream generation. section 9.1
- Upload the processed OpenAPI definition to an API artifact store for retrieval by later pipeline stages and consumers. section 9.1 section 9.1.1
Generated external API definition
A product API repository can create build-output, bundle openapi.yaml with Redocly CLI, filter x-internal endpoints, remove unused schemas and responses, sort fields, and lint the final api.yaml. The pipeline then stores that processed definition in Apicurio API Registry, where the developer portal can generate API reference material and SDKs can consume it.
