Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Centralize state management #138

Closed
PaulFarault opened this issue Jan 10, 2023 · 0 comments · Fixed by #157
Closed

Centralize state management #138

PaulFarault opened this issue Jan 10, 2023 · 0 comments · Fixed by #157
Assignees
Labels
enhancement New feature or request

Comments

@PaulFarault
Copy link
Contributor

For now, the global state only holds the list of services while local states hold all other configuration values (per service, per component). We should investigate about having a global state that hold everything (as the GET /api/v1/services, which is used to get the list of the services, return also all config values), and local hooks that actualize this global state.

@PaulFarault PaulFarault added the enhancement New feature or request label Jan 10, 2023
@PaulFarault PaulFarault self-assigned this Feb 2, 2023
This was referenced Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant