Evaluate consumers of OpenAPI

[lofidevops]

SN-1142

From https://openapi.tools we have identified potential consumers of OpenAPI schemas, but they only support OpenAPI 3.0. Options include:

1. translate 3.1 schemas to 3.0, consume from there
2. update consumers to ingest 3.1 schemas

This ticket explores option 2. (It's probably worth trialing these tools first via option 1 to confirm they add value.)

Connexion 🐍 📝

• OpenAPI Specification 3.1 spec-first/connexion#1396
  • Support for v2020-12 and v2019 drafts python-jsonschema/jsonschema#782
  • Add support for draft 2020-12 python-jsonschema/jsonschema#817
  • Spec 3.1 schema python-openapi/openapi-spec-validator#111
  • Other issues for 3.1 support in https://github.com/p1c2u/openapi-spec-validator ?
    • None. Now supports 3.1.
  • See also Roadmap for Connexion 3.0 spec-first/connexion#1395

Fuzzers

• https://github.com/matusf/openapi-fuzzer (Rust 🦀 ) no clear plan to adopt 3.1
• https://github.com/vwt-digital/openapi3-fuzzer/tree/master (Python 🐍 ) no clear plan to adopt 3.1
• https://github.com/KissPeter/APIFuzzer (Python 🐍 ) no clear plan to adopt 3.1

See also

https://www.openapis.org/blog/2021/02/16/migrating-from-openapi-3-0-to-3-1-0

[lofidevops]

We are currently using Connexion by downgrading 3.1 schemas to 3.0. This is sufficient for now.