Commit Graph

7 Commits (d2279e8afaf3649a8433a7ccae37b692af53d05c)

Author SHA1 Message Date
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
Iris Scholten 43afa38b0a
Remove check for flux ping when adding and updating flux service (#4361) 2018-09-05 11:01:20 -07:00
Alirie Gray 0f393b8bf3 Flux/connections page (#4026)
* Load services on manages sources page

Co-authored-by: Alirie Gray <alirie.gray@gmail.com>

* Add Flux dropdown on manage sources page

Co-authored-by: Alirie Gray <alirie.gray@gmail.com>

* Add flux connection dropdown with create, select, and update

Co-authored-by: Alirie Gray <alirie.gray@gmail.com>

* Prevent creation of Flux connection with duplicate name

Fixed bug where refreshing page allowed for Flux or connections
with duplicate names to be created

Co-authored-by: Iris Scholten <ischolten.is@gmail.com>

* Add ability to delete a FluxService from the fluxservice dropdown

Co-authored-by: Alirie Gray <alirie.gray@gmail.com>

* Change FluxPage to use the active flux connection set by FluxConnectionPage

Co-authored-by: Alirie Gray <alirie.gray@gmail.com>

* Ensure that only flux services are loaded into redux services

* Polish styles for Flux Connection Page

Co-authored-by: Alex Paxton <thealexpaxton@gmail.com>
Co-authored-by: Alirie Gray <alirie.gray@gmail.com>

* Add pingflux as a part of adding and updating a flux service

Co-authored-by: Chris Goller <goller@gmail.com>
Co-authored-by: Alirie Gray <alirie.gray@gmail.com>

* Add Swagger routes and definitions for Service endpoints

Co-authored-by: Iris Scholten <ischolten.is@gmail.com>

* Replace flux overlay with redirect to flux connections pages

* Add test for FluxConnectionPage

Co-authored-by: Iris Scholten <ischolten.is@gmail.com>

* Replace hard-coded string with enum

* Use active from metadata instead of service object in ServiceDropdown

Co-authored-by: Iris Scholten <ischolten.is@gmail.com>

* Add generic for getDeep on service metadata property

* Capitalize enum constant values in FluxFormMode

* Show error notification when user reaches edit route for nonexistant flux

Co-authored-by: Iris Scholten <ischolten.is@gmail.com>

* Add tests for FluxDropdown

* Update types for async functions
2018-07-26 18:16:02 -07:00
Andrew Watkins ed4a6f24e5
Change IFQL to Flux 2018-06-05 10:57:19 -07:00
Chris Goller f74f5a378f feat(server/services): add metadata for services 2018-05-21 10:45:28 -07:00
Chris Goller 45a981911d feat(server/services): add source id and source link to all services 2018-05-21 10:45:28 -07:00
Chris Goller 5cd8cc7cdd feat(server/services): add generic services scoped under server 2018-05-21 10:45:27 -07:00