Add component-level targeting to start, stop, and restart
Allow start/stop/restart to target a single component via <service>/<component> syntax, matching deploy/logs/purge. When a component is specified, start/stop skip toggling the service-level active flag. Agent-side filtering returns NotFound for unknown components. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -92,6 +92,7 @@ message ComponentResult {
|
||||
|
||||
message StopServiceRequest {
|
||||
string name = 1;
|
||||
string component = 2;
|
||||
}
|
||||
|
||||
message StopServiceResponse {
|
||||
@@ -100,6 +101,7 @@ message StopServiceResponse {
|
||||
|
||||
message StartServiceRequest {
|
||||
string name = 1;
|
||||
string component = 2;
|
||||
}
|
||||
|
||||
message StartServiceResponse {
|
||||
@@ -108,6 +110,7 @@ message StartServiceResponse {
|
||||
|
||||
message RestartServiceRequest {
|
||||
string name = 1;
|
||||
string component = 2;
|
||||
}
|
||||
|
||||
message RestartServiceResponse {
|
||||
|
||||
Reference in New Issue
Block a user