kongfig - diff against API and automatically delete what's not on config

When automating kong config deployments with kong, sometimes changes are made that remove elements from kong. I believe kongfig caters for this with the ensure: present|absent property on each object.

This however creates a great deal of technical debt. Cannot be removed until it’s been deployed everywhere, which is difficult to keep track of.

It would be great if kongfig would compare the config file given to it against what’s on kong’s admin API, and proceed to delete anything on the API that’s not on config.

This way we could fully automate deployments without littering our config files with @todos and technical debt.

[ankona]

I didn’t want to thumbs-down you without an explanation. I felt just as odd about the ensure property at first, but we ended up using it to our advantage (or disadvantage from another viewpoint, I suppose). Rather than centrally manage our ‘one true kongfig’ for all of our apis, each microservice/repository has it’s own. We like that model because it ensures a minimal deployment, less chance of conflicts as those services get released so often, and no dependent builds in jenkins.

I do like the suggestion by @kjsteuer to allow it to be an additional apply option, though. Something like:

kongfig apply --path kongfig.yml --host x --ensureoff

[bparthu]

When are we expecting this feature ? - #107