Is it possible to keep Kong DB-Less running, updating the local yaml file in the file system. Then somehow reload that yaml of config while Kong is taking active traffic without interrupting anything? Or does Kong DBLESS when doing a config change(new routes/service/consumers/plugins) require like a rolling redeploy alongside pulling in the new config to not impact hot traffic?
Would make my life easier if Kong could just keep active running for traffic and when a spec gets uploaded and I can refresh the resources based on the new doc impact free somehow(basically Kong just continues doing its thing and uses old YAML resources until new YAML is fully parsed and the resources are ready for use).
Any masterminds behind Kong DB-less have ideas here?