Hello Any help on the following use-case ? We are deploying Kong over Heroku, and we would like to be able to take advantage of Heroku github binding, and basically versionning our config. The final goal is to have a Kong instance which is controllable by some sort of “config file” versionned inside github, automatically deployed on Heroku, bringing automation, versionning in the process.
We would then be able to:
Have a versionned config file on github
Edit and push it
It redeploys automatically inside Heroku
It restarts the Kong
New routes are applied
And to “Roolback” from here to any previous point, using heroku github binding.
By nature, Kong “configuration” (I mean APIs configuration) is inside a datastore, which is not really meant to be manipulated directly, and the only stuff I found to make it declarative is https://github.com/mybuilder/kongfig which seems a good idea, but is using an old release of Kong, adds a middle Layer, and is not widely maintained.
Any thoughts / experiences / warning / advice on this ?