You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dyn/memcache_v1.projects.locations.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -135,7 +135,7 @@ <h3>Method Details</h3>
135
135
136
136
Args:
137
137
name: string, The resource that owns the locations collection, if applicable. (required)
138
-
filter: string, A filter to narrow down results to a preferred subset. The filtering language accepts strings like "displayName=tokyo", and is documented in more detail in [AIP-160](https://google.aip.dev/160).
138
+
filter: string, A filter to narrow down results to a preferred subset. The filtering language accepts strings like `"displayName=tokyo"`, and is documented in more detail in [AIP-160](https://google.aip.dev/160).
139
139
pageSize: integer, The maximum number of results to return. If not set, the service selects a default.
140
140
pageToken: string, A page token received from the `next_page_token` field in the response. Send that page token to receive the subsequent page.
<pclass="firstline">Updates the defined Memcached parameters for an existing instance. This method only stages the parameters, it must be followed by `ApplyParameters` to apply the parameters to nodes of the Memcached instance.</p>
instance: string, Required. Memcache instance resource name using the form: `projects/{project_id}/locations/{location_id}/instances/{instance_id}` where `location_id` refers to a GCP region. (required)
621
+
body: object, The request body.
622
+
The object takes the form of:
623
+
624
+
{ # Request for RescheduleMaintenance.
625
+
"rescheduleType": "A String", # Required. If reschedule type is SPECIFIC_TIME, must set up schedule_time as well.
626
+
"scheduleTime": "A String", # Timestamp when the maintenance shall be rescheduled to if reschedule_type=SPECIFIC_TIME, in RFC 3339 format, for example `2012-11-15T16:19:00.094Z`.
627
+
}
628
+
629
+
x__xgafv: string, V1 error format.
630
+
Allowed values
631
+
1 - v1 error format
632
+
2 - v2 error format
633
+
634
+
Returns:
635
+
An object of the form:
636
+
637
+
{ # This resource represents a long-running operation that is the result of a network API call.
638
+
"done": True or False, # If the value is `false`, it means the operation is still in progress. If `true`, the operation is completed, and either `error` or `response` is available.
639
+
"error": { # The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors). # The error result of the operation in case of failure or cancellation.
640
+
"code": 42, # The status code, which should be an enum value of google.rpc.Code.
641
+
"details": [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.
642
+
{
643
+
"a_key": "", # Properties of the object. Contains field @type with type URL.
644
+
},
645
+
],
646
+
"message": "A String", # A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client.
647
+
},
648
+
"metadata": { # Service-specific metadata associated with the operation. It typically contains progress information and common metadata such as create time. Some services might not provide such metadata. Any method that returns a long-running operation should document the metadata type, if any.
649
+
"a_key": "", # Properties of the object. Contains field @type with type URL.
650
+
},
651
+
"name": "A String", # The server-assigned name, which is only unique within the same service that originally returns it. If you use the default HTTP mapping, the `name` should be a resource name ending with `operations/{unique_id}`.
652
+
"response": { # The normal response of the operation in case of success. If the original method returns no data on success, such as `Delete`, the response is `google.protobuf.Empty`. If the original method is standard `Get`/`Create`/`Update`, the response should be the resource. For other methods, the response should have the type `XxxResponse`, where `Xxx` is the original method name. For example, if the original method name is `TakeSnapshot()`, the inferred response type is `TakeSnapshotResponse`.
653
+
"a_key": "", # Properties of the object. Contains field @type with type URL.
<pre>Updates the defined Memcached parameters for an existing instance. This method only stages the parameters, it must be followed by `ApplyParameters` to apply the parameters to nodes of the Memcached instance.
Copy file name to clipboardExpand all lines: docs/dyn/memcache_v1.projects.locations.operations.html
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -113,7 +113,7 @@ <h3>Method Details</h3>
113
113
Returns:
114
114
An object of the form:
115
115
116
-
{ # A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); } The JSON representation for `Empty` is empty JSON object `{}`.
116
+
{ # A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }
117
117
}</pre>
118
118
</div>
119
119
@@ -136,7 +136,7 @@ <h3>Method Details</h3>
136
136
Returns:
137
137
An object of the form:
138
138
139
-
{ # A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); } The JSON representation for `Empty` is empty JSON object `{}`.
139
+
{ # A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }
Copy file name to clipboardExpand all lines: docs/dyn/memcache_v1beta2.projects.locations.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -135,7 +135,7 @@ <h3>Method Details</h3>
135
135
136
136
Args:
137
137
name: string, The resource that owns the locations collection, if applicable. (required)
138
-
filter: string, A filter to narrow down results to a preferred subset. The filtering language accepts strings like "displayName=tokyo", and is documented in more detail in [AIP-160](https://google.aip.dev/160).
138
+
filter: string, A filter to narrow down results to a preferred subset. The filtering language accepts strings like `"displayName=tokyo"`, and is documented in more detail in [AIP-160](https://google.aip.dev/160).
139
139
pageSize: integer, The maximum number of results to return. If not set, the service selects a default.
140
140
pageToken: string, A page token received from the `next_page_token` field in the response. Send that page token to receive the subsequent page.
<pclass="firstline">Updates the defined Memcached parameters for an existing instance. This method only stages the parameters, it must be followed by `ApplyParameters` to apply the parameters to nodes of the Memcached instance.</p>
<pre>Performs the apply phase of the RescheduleMaintenance verb.
674
+
675
+
Args:
676
+
instance: string, Required. Memcache instance resource name using the form: `projects/{project_id}/locations/{location_id}/instances/{instance_id}` where `location_id` refers to a GCP region. (required)
677
+
body: object, The request body.
678
+
The object takes the form of:
679
+
680
+
{ # Request for RescheduleMaintenance.
681
+
"rescheduleType": "A String", # Required. If reschedule type is SPECIFIC_TIME, must set up schedule_time as well.
682
+
"scheduleTime": "A String", # Timestamp when the maintenance shall be rescheduled to if reschedule_type=SPECIFIC_TIME, in RFC 3339 format, for example `2012-11-15T16:19:00.094Z`.
683
+
}
684
+
685
+
x__xgafv: string, V1 error format.
686
+
Allowed values
687
+
1 - v1 error format
688
+
2 - v2 error format
689
+
690
+
Returns:
691
+
An object of the form:
692
+
693
+
{ # This resource represents a long-running operation that is the result of a network API call.
694
+
"done": True or False, # If the value is `false`, it means the operation is still in progress. If `true`, the operation is completed, and either `error` or `response` is available.
695
+
"error": { # The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors). # The error result of the operation in case of failure or cancellation.
696
+
"code": 42, # The status code, which should be an enum value of google.rpc.Code.
697
+
"details": [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.
698
+
{
699
+
"a_key": "", # Properties of the object. Contains field @type with type URL.
700
+
},
701
+
],
702
+
"message": "A String", # A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client.
703
+
},
704
+
"metadata": { # Service-specific metadata associated with the operation. It typically contains progress information and common metadata such as create time. Some services might not provide such metadata. Any method that returns a long-running operation should document the metadata type, if any.
705
+
"a_key": "", # Properties of the object. Contains field @type with type URL.
706
+
},
707
+
"name": "A String", # The server-assigned name, which is only unique within the same service that originally returns it. If you use the default HTTP mapping, the `name` should be a resource name ending with `operations/{unique_id}`.
708
+
"response": { # The normal response of the operation in case of success. If the original method returns no data on success, such as `Delete`, the response is `google.protobuf.Empty`. If the original method is standard `Get`/`Create`/`Update`, the response should be the resource. For other methods, the response should have the type `XxxResponse`, where `Xxx` is the original method name. For example, if the original method name is `TakeSnapshot()`, the inferred response type is `TakeSnapshotResponse`.
709
+
"a_key": "", # Properties of the object. Contains field @type with type URL.
<pre>Updates the defined Memcached parameters for an existing instance. This method only stages the parameters, it must be followed by `ApplyParameters` to apply the parameters to nodes of the Memcached instance.
Copy file name to clipboardExpand all lines: docs/dyn/memcache_v1beta2.projects.locations.operations.html
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -113,7 +113,7 @@ <h3>Method Details</h3>
113
113
Returns:
114
114
An object of the form:
115
115
116
-
{ # A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); } The JSON representation for `Empty` is empty JSON object `{}`.
116
+
{ # A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }
117
117
}</pre>
118
118
</div>
119
119
@@ -136,7 +136,7 @@ <h3>Method Details</h3>
136
136
Returns:
137
137
An object of the form:
138
138
139
-
{ # A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); } The JSON representation for `Empty` is empty JSON object `{}`.
139
+
{ # A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }
0 commit comments