In CD environment, I would like to see a single source of truth (git), and go through usual engineering workflow for API contracts too, with review/collaboration on API specifications (aka. typically Pull/Merge Request on specification changes) and manage API specifications as code…
That would mean asking developers to edit source files (yawl, json) instead of the nice designer UI provided, but that approach can remove manual edits, allow listing, improve consistency and in the end quality. Use the UI for junior, to setup, but the industrialise the next steps when the team matures.
Do you have a way to deploy Tyk api routes, specifications, documentations, secrets (git-crypt) through a Git-based CD flow?
I have seen an article on tyk-git as a way to export the config changes done in the designer UI, as an output of development, and then move it across the deployment lifecycle. Is that the recommended approach?