Versioning Governance Rules

Rules can be defined to govern the information provided for each API, leveraging the OpenAPI or AsynCaPI contracts, but then apply specific ruling looking for common versioning patterns in the path, parameters, headers, and other details of an API, meeting specific guidelines regarding what information is needed.

Does this provide what you need? Let us know by submitting issue!

Versioning governance rules provide a base of YAML or JSON rules that can be applied to OpenAPI or AsyncAPI contracts, checking for common versioning patterns in the path, parameters, headers, and other elements of an API. Rules can be defined centrally by governance leadership, or locally within teams, and then applied either at design, develop, or build time in a manual or automated way depending on the objectives of team, department, organization, or industry-wide governance.

Related Links


Blueprints

Return to Main Page

This provides a link back to the home page if you need it.