Consul support? #1703
Description
Is your feature request related to a problem? Please describe.
Not really? I'm not yet using gravity, just reviewing + evaluating it for my own use-cases. Currently I'm running PowerDNS for DNS, Kea for DHCP, & am setting up a tFTP server for iPXE boot. For tFTP, I used to use tftp-hpa, but I'm evaluating other options for it (some of which integrate DNS/DHCP/tFTP, like gravity).
Gravity would probably be great to replace at least Kea + provide a tFTP server, though not yet sure about replacing PowerDNS.
Ideally, gravity could just proxy DNS to PowerDNS & be configured with a TSIG key for DDNS updates for DHCP clients. Though that's probably a separate issue and not a priority.
Describe the solution you'd like
Consul support for distributed key-value storage.
Describe alternatives you've considered
Deploying etcd. I'm already running & using consul though, so I'd need to run two key-value stores (consul + etcd), along with the accompanying tools & processes (e.g. backups, monitoring, etc).
Additional context
Not really expecting consul support to be a priority. Not having looked at the codebase yet, I'm curious how much effort it would be to implement consul support. If it's relatively low-effort, then it might be worth doing, otherwise no biggie.