Greg f0d5e5abef chore: add a KV layer prior to adding an etcd implementation (#5349) ... * Bolt to kv/bolt * Remove unused code * Remove unused roles code * Remove unused duplicate Makefile * Clean up bolt implementation and start layering in an interface for another store * Layer in kv interface * Continue layering in kv interface * Remove circuitbreaker things * Move cell stuff out * Convert cell logic to kv interface * Start adding config logic to kv interface, likely will remain bolt only * Get to compile with bolt kv before moving too far forward * Start removing dead dashboard code * Add generic kv implementation for dashboards * Convert layouts to kv interface * Migrate mappings to kv layer * Migrate org_config to kv layer * Migrate organizations to kv layer * Migrate servers to kv layer * Migrate sources to kv layer * Migrate users to kv layer * Start removing unused migration logic Since there is a migration path for users via updating to 1.7.x line then to 1.8, there isn't any real reason to continue supporting migrating from a version ~2 years old. * Cleaning up bolt dead codes * Re-add disabled code * Migrate tests over to kv layer * Migrate config to kv layer * Create default organization * Remove etcd for now * Improve new client and new service implementations * Uncomment bolt build tests * Add layouts test * Add more dashboard tests to kv		2020-01-21 09:26:23 -07:00
..
roles.go	chore: add a KV layer prior to adding an etcd implementation (#5349)	2020-01-21 09:26:23 -07:00