Support loading Tyk OAS API Definition from different sources

[caroltyk]

Hello Tyk Operator community!

We’ve recently introduced a new custom resource in the develop branch, TykOasApiDefinition, to facilitate the management of Tyk OAS APIs. Currently, users can conveniently store their OAS API Definitions in a ConfigMap, which can then be referenced from the CRD. For a quick example, check out this TykOasApiDefinition.

Looking ahead, we aim to enhance the flexibility of Tyk Operator by supporting various sources for loading OAS APIs. This brings us to an important question: What should be the primary source of truth for your specific use case?

We’d love to hear from you about your preferred workflow and how you manage your OAS definitions. Here are a few prompts to get the discussion started:

• How do you currently generate your OAS definitions?
• Are they version controlled in your workflow?
• Would you prefer accessing them through a dedicated endpoint within your workload?

Your insights will greatly inform our development efforts and ensure that Tyk Operator aligns closely with your needs. Please share your thoughts and suggestions below!

Happy discussing!