Choose the schema definition format

[achichenin]

• yamale
• jsonschema (for yaml)
• k8s based?

[achichenin]

Some thoughts so far (raw voice recording):

We started with the simple Yaml based symbol available in Python but then we realized that we also need to support custom resource definitions in Kubernetes so we wanted to use something compatible with Kubernetes disposable they use something very similar to the open API V3 specification.

They still create an additional scheme on top of it we don't really want to use that their custom resource definition format great for two lynx and a lot of Kubernetes related stop that we don't really want to use instead of directly using this we will use open API V3 we have a couple of libraries which are quite lightweight and will support the open API V3 specification.

We'll probably need to create a scene converter that will convert the open API V3 custom resource definition for Math and will maintain it and store it in our story but still allow us to update the manual just actually yeah we will need to create the tooling that will interact wastegate maybe and automatically whenever we update thesaurus schema formats update their customer service that if you need something for customer service definition actually so this is very simple and should work quite fine.

[achichenin]

Modern modules for python for OpenAPI v3 (related):

• https://github.com/p1c2u/openapi-spec-validator
• https://github.com/p1c2u/openapi-schema-validator

[achichenin]

Some important things: https://apisyouwonthate.com/blog/openapi-v31-and-json-schema-2019-09

[achichenin]

https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.1.0.md