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

Support custom RacksDB infrastructure name #351

Merged
merged 6 commits into from
Sep 20, 2024
Merged

Support custom RacksDB infrastructure name #351

merged 6 commits into from
Sep 20, 2024

Conversation

rezib
Copy link
Contributor

@rezib rezib commented Sep 19, 2024

fix #348

@rezib rezib added the feature New feature or enhancement to develop. label Sep 19, 2024
@rezib rezib added this to the v4.0.0 milestone Sep 19, 2024
@rezib rezib self-assigned this Sep 19, 2024
This will be needed by the frontend to request the right infrastructure
in RacksDB eventually.
Return RacksDB infrastructure name of every clusters in /clusters
endpoint.
Requests RacksDB with the infrastructure name retrieved from the
/clusters endpoint of the gateway, and stop assuming it is necessary the
cluster name.

fix #348
When UI name is different from cluster name, add RacksDB infrastructure
name in agent configuration file.
@rezib rezib merged commit adf54f6 into main Sep 20, 2024
1 check passed
@github-actions github-actions bot locked and limited conversation to collaborators Sep 20, 2024
@rezib rezib deleted the pr/feat-348 branch October 9, 2024 15:14
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature New feature or enhancement to develop.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support custom RacksDB infrastructure name in alternative to cluster name
1 participant