linkedin/cruise-control

cruise-control-client is not API complete with cruise-control

Open

#897 opened on Aug 12, 2019

View on GitHub
 (4 comments) (0 reactions) (1 assignee)Java (649 forks)auto 404
functionalitygood first issueusability

Repository metrics

Stars
 (3,036 stars)
PR merge metrics
 (PR metrics pending)

Description

Problem

Currently, cruise-control-client lags behind cruise-control in the parameters that are available to some of its endpoints.

All the endpoints are there, so a user with the cruise-control documentation would be able to use cruise-control-client's --add-parameter flag to achieve future compatibility.

Proposal

cruise-control-client should be updated to reflect all of the parameters that cruise-control provides for its endpoints

Contributor guide

Research direction
Compare the API endpoint parameters between cruise control and cruise control client to identify missing parameters.
Tech stack
java
Domain
backendapiinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaKafka
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60