-
Notifications
You must be signed in to change notification settings - Fork 217
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
Identify Stargate nodes #1179
Identify Stargate nodes #1179
Conversation
…return property via the NodeStatus object
…types of nodes to detect
…te nodes in selection options for creating repairs/schedules
…eaper into jdinoto-identify-stargate * 'master' of https://github.com/thelastpickle/cassandra-reaper: No need to install bower in GHAs directly UI tooling update * Remove the external dependency on bower by moving it within the npm dependencies and scripts * Consolidates the UI dev/build process to be exclusively controlled through npm ninja-fix: Correct default keyspace value in Docker documentation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It all looks great @jdonenine, thanks!
You'll need to add a proper license header to the newly created node-utils.js
file so that the build can go through.
Ah the file header, gets me every time! Added in the last commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Finally, Stargate nodes won't appear as down anymore 🤗
Thanks @jdonenine !
Add the ability to identify stargate nodes and distinguish them in the UI.
cluster/{name}
endpoint response to include a newtype
property, will either beCASSANDRA
orSTARGATE
(Stargate)
label to the modal title as well as a display field calledNode Type
which will either beCassandra
orStargate
Node
select options when creating repairs/schedules.Fixes #1145