-
Notifications
You must be signed in to change notification settings - Fork 116
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
Add support for Operator Autopilot API #206
Comments
The API But if you want to do a PR to add support for Autopilot API feel free :) |
@rhughes1 Did you find your way to implement what you wanted? |
@pierresouchay believe I did... Although I think I could open a PR for an autopilot endpoint. My only concern is being able to make valid unit tests :s |
@rhughes1 If you don't know how to add unit test, try submitting it, we will help you write the unit tests |
@rhughes1 Merge upstream and released as version 2.4.0 (will be available in rubygems in a few minutes). If you want to add support for more endpoints of Autopilot API, feel free. Thanks a lot for your contribution! |
I've been trying to look through the documentation to find a way to pull the health of the cluster using the Autopilot API. In particular I'm looking to see if the nodes are voters or not.
Below would be an example of getting the current Autopilot configuration:
Below would be an example of what I was thinking it would look like for getting the health, configuration and updating the configuration:
I'm curious if there's some workaround that I'm not aware of to get the voter status in the cluster?
The text was updated successfully, but these errors were encountered: