suguo
/
googleapis
0
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Synchronize new proto changes.

This commit is contained in:
Google APIs 2017-08-03 15:03:30 -07:00
parent cd94ce883b
commit 7a9e96e169
1 changed files with 31 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
google/api/servicecontrol/v1/service_controller.proto
View File

@ -1,4 +1,4 @@
// Copyright 2016 Google Inc.
// Copyright 2017 Google Inc.
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
@ -39,9 +39,11 @@ service ServiceController {
// operation is executed.
//
// If feasible, the client should cache the check results and reuse them for
// up to 60s. In case of server errors, the client may rely on the cached
// 60 seconds. In case of server errors, the client can rely on the cached
// results for longer time.
//
// NOTE: the `CheckRequest` has the size limit of 64KB.
//
// This method requires the `servicemanagement.services.check` permission
// on the specified service. For more information, see
// [Google Cloud IAM](https://cloud.google.com/iam).
@ -49,14 +51,16 @@ service ServiceController {
option (google.api.http) = { post: "/v1/services/{service_name}:check" body: "*" };
}
// Reports operations to Google Service Control. It should be called
// after the operation is completed.
// Reports operation results to Google Service Control, such as logs and
// metrics. It should be called after an operation is completed.
//
// If feasible, the client should aggregate reporting data for up to 5s to
// reduce API traffic. Limiting aggregation to 5s is to reduce data loss
// during client crashes. Clients should carefully choose the aggregation
// window to avoid data loss risk more than 0.01% for business and
// compliance reasons.
// If feasible, the client should aggregate reporting data for up to 5
// seconds to reduce API traffic. Limiting aggregation to 5 seconds is to
// reduce data loss during client crashes. Clients should carefully choose
// the aggregation time window to avoid data loss risk more than 0.01%
// for business and compliance reasons.
//
// NOTE: the `ReportRequest` has the size limit of 1MB.
//
// This method requires the `servicemanagement.services.report` permission
// on the specified service. For more information, see
@ -87,6 +91,18 @@ message CheckRequest {
// Response message for the Check method.
message CheckResponse {
message CheckInfo {
// Consumer info of this check.
ConsumerInfo consumer_info = 2;
}
// `ConsumerInfo` provides information about the consumer project.
message ConsumerInfo {
// The Google cloud project number, e.g. 1234567890. A value of 0 indicates
// no project number is found.
int64 project_number = 1;
}
// The same operation_id value used in the CheckRequest.
// Used for logging and diagnostics purposes.
string operation_id = 1;
@ -100,6 +116,9 @@ message CheckResponse {
// The actual config id used to process the request.
string service_config_id = 5;
// Feedback data returned from the server during processing a Check request.
CheckInfo check_info = 6;
}
// Request message for the Report method.
@ -152,8 +171,9 @@ message ReportResponse {
// `Operations` in the request succeeded. Each
// `Operation` that failed processing has a corresponding item
// in this list.
// 3. A failed RPC status indicates a complete failure where none of the
// `Operations` in the request succeeded.
// 3. A failed RPC status indicates a general non-deterministic failure.
// When this happens, it's impossible to know which of the
// 'Operations' in the request succeeded or failed.
repeated ReportError report_errors = 1;
// The actual config id used to process the request.