Add support for RepairRun REST resource #6
Conversation
| // CreateRepairRun creates a new repair run for the given cluster and keyspace. Does not actually trigger the run: | ||
| // creating a repair run includes generating the repair segments. Returns the id of the newly-created repair run if | ||
| // successful. The owner name can be any string identifying the owner. | ||
| CreateRepairRun( |
There was a problem hiding this comment.
Maybe this is a question for @adejanovski. When I create a RepairRun, do I typically want to start it?
There was a problem hiding this comment.
It depends 😅
So, I'd say not necessarily instantly if you first want to check how many segments you end up with.
|
@adejanovski @jeffbanks or @jsanda if everything looks good, would you mind giving your approval please? |
Oh you are absolutely right, my bad. I can offer to change the RepairRun-related methods real quick. The I'd suggest to leave the pre-existing methods (GetCluster, etc...) as is and change them later in a follow-up PR. |
|
Kudos, SonarCloud Quality Gate passed!
|
|
Thanks for making the change @adutra ! LGTM ✅ |
While API design is being discussed in #5, I'm opening this PR to get the ball rolling. If the design principles change, I will amend it accordingly.
This PR contains a few commits so far:
Commits can be reviewed separately.
┆Issue is synchronized with this Jira Bug by Unito