Currently Apidog supports an automatic backup to Github (once a day) of a defined openapi specification. We were really pleased to see this feature introduced as we want to establish an automatic process of creating an infra-repo with the openapi specifications of all our backend microservices.
Unfortunately the current implementation in Apidog is not very convenient for the process we want to achieve. Here is the process that we try to implement:
- Create an Apiversion in Apdiog
- Create a new openapi specification with an increased version number matching the Apiversion
- Export this Apiversion (branch) to Github
- Process the openapi specification in Github Actions, e.g. to trigger code generations.
We implemented this process with the current automatic backup option in Apidog, but we have found out that there are major issues:
-
A LOT of unnecessary backups: As each openapi specification is based on an Apiversion there will be no further changes to this specification. So a daily automatic backup will trigger dozens (and hundreds in the Future) of unnecessary workflow runs each day in our Github repository.
-
Automatic backup of main: It is no use in our process as the automatic backup will not version changes that have been made. We would be exporting Version 1.0.0 forever.
In order to solve this, i would greatly ask you to implement this feature:
- One-time export: In addition to the automatic backup create a one-time export to Github without the cron job
Thank you very much and keep up the good work,
Fritz