OMGeeky/google-apis-rs
1
0
Fork 0
mirror of https://github.com/OMGeeky/google-apis-rs.git synced 2026-02-23 15:49:49 +01:00
Code Issues Packages Projects Releases Wiki Activity

make regen-apis

Browse Source
This commit is contained in:
OMGeeky
2023-10-21 02:11:31 +02:00
parent 557df5b43f
commit bcacb792b1
964 changed files with 11866 additions and 11866 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
gen/memcache1/README.md
View File

@@ -11,7 +11,7 @@ Everything else about the *Cloud Memorystore for Memcached* *v1* API can be foun
[official documentation site](https://cloud.google.com/memorystore/).
# Features
Handle the following *Resources* with ease from the central [hub](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/CloudMemorystoreForMemcached) ...
Handle the following *Resources* with ease from the central [hub](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/CloudMemorystoreForMemcached) ...
* projects
* [*locations get*](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/api::ProjectLocationGetCall), [*locations instances apply parameters*](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/api::ProjectLocationInstanceApplyParameterCall), [*locations instances create*](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/api::ProjectLocationInstanceCreateCall), [*locations instances delete*](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/api::ProjectLocationInstanceDeleteCall), [*locations instances get*](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/api::ProjectLocationInstanceGetCall), [*locations instances list*](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/api::ProjectLocationInstanceListCall), [*locations instances patch*](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/api::ProjectLocationInstancePatchCall), [*locations instances reschedule maintenance*](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/api::ProjectLocationInstanceRescheduleMaintenanceCall), [*locations instances update parameters*](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/api::ProjectLocationInstanceUpdateParameterCall), [*locations list*](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/api::ProjectLocationListCall), [*locations operations cancel*](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/api::ProjectLocationOperationCancelCall), [*locations operations delete*](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/api::ProjectLocationOperationDeleteCall), [*locations operations get*](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/api::ProjectLocationOperationGetCall) and [*locations operations list*](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/api::ProjectLocationOperationListCall)
@@ -56,8 +56,8 @@ let r = hub.projects().locations_instances_update_parameters(...).doit().await
let r = hub.projects().locations_operations_get(...).doit().await
```
The `resource()` and `activity(...)` calls create [builders][builder-pattern]. The second one dealing with `Activities`
supports various methods to configure the impending operation (not shown here). It is made such that all required arguments have to be
The `resource()` and `activity(...)` calls create [builders][builder-pattern]. The second one dealing with `Activities`
supports various methods to configure the impending operation (not shown here). It is made such that all required arguments have to be
specified right away (i.e. `(...)`), whereas all optional ones can be [build up][builder-pattern] as desired.
The `doit()` method performs the actual communication with the server and returns the respective result.
@@ -85,12 +85,12 @@ use memcache1::{Result, Error};
use std::default::Default;
use memcache1::{CloudMemorystoreForMemcached, oauth2, hyper, hyper_rustls, chrono, FieldMask};
// Get an ApplicationSecret instance by some means. It contains the `client_id` and
// Get an ApplicationSecret instance by some means. It contains the `client_id` and
// `client_secret`, among other things.
let secret: oauth2::ApplicationSecret = Default::default();
// Instantiate the authenticator. It will choose a suitable authentication flow for you,
// Instantiate the authenticator. It will choose a suitable authentication flow for you,
// unless you replace `None` with the desired Flow.
// Provide your own `AuthenticatorDelegate` to adjust the way it operates and get feedback about
// Provide your own `AuthenticatorDelegate` to adjust the way it operates and get feedback about
// what's going on. You probably want to bring in your own `TokenStorage` to persist tokens and
// retrieve them from storage.
let auth = oauth2::InstalledFlowAuthenticator::builder(
@@ -132,10 +132,10 @@ match result {
## Handling Errors
All errors produced by the system are provided either as [Result](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/client::Result) enumeration as return value of
the doit() methods, or handed as possibly intermediate results to either the
the doit() methods, or handed as possibly intermediate results to either the
[Hub Delegate](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/client::Delegate), or the [Authenticator Delegate](https://docs.rs/yup-oauth2/*/yup_oauth2/trait.AuthenticatorDelegate.html).
When delegates handle errors or intermediate values, they may have a chance to instruct the system to retry. This
When delegates handle errors or intermediate values, they may have a chance to instruct the system to retry. This
makes the system potentially resilient to all kinds of errors.
## Uploads and Downloads
@@ -145,25 +145,25 @@ If such a method also supports a [Response Result](https://docs.rs/google-memcac
You can see it as meta-data for the actual media. To trigger a media download, you will have to set up the builder by making
this call: `.param("alt", "media")`.
Methods supporting uploads can do so using up to 2 different protocols:
*simple* and *resumable*. The distinctiveness of each is represented by customized
Methods supporting uploads can do so using up to 2 different protocols:
*simple* and *resumable*. The distinctiveness of each is represented by customized
`doit(...)` methods, which are then named `upload(...)` and `upload_resumable(...)` respectively.
## Customization and Callbacks
You may alter the way an `doit()` method is called by providing a [delegate](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/client::Delegate) to the
[Method Builder](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/client::CallBuilder) before making the final `doit()` call.
Respective methods will be called to provide progress information, as well as determine whether the system should
You may alter the way an `doit()` method is called by providing a [delegate](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/client::Delegate) to the
[Method Builder](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/client::CallBuilder) before making the final `doit()` call.
Respective methods will be called to provide progress information, as well as determine whether the system should
retry on failure.
The [delegate trait](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/client::Delegate) is default-implemented, allowing you to customize it with minimal effort.
## Optional Parts in Server-Requests
All structures provided by this library are made to be [encodable](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/client::RequestValue) and
[decodable](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/client::ResponseResult) via *json*. Optionals are used to indicate that partial requests are responses
All structures provided by this library are made to be [encodable](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/client::RequestValue) and
[decodable](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/client::ResponseResult) via *json*. Optionals are used to indicate that partial requests are responses
are valid.
Most optionals are are considered [Parts](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/client::Part) which are identifiable by name, which will be sent to
Most optionals are are considered [Parts](https://docs.rs/google-memcache1/5.0.3+20230103/google_memcache1/client::Part) which are identifiable by name, which will be sent to
the server to indicate either the set parts of the request or the desired parts in the response.
## Builder Arguments
@@ -182,7 +182,7 @@ Arguments will always be copied or cloned into the builder, to make them indepen
[google-go-api]: https://github.com/google/google-api-go-client
# License
The **memcache1** library was generated by Sebastian Thiel, and is placed
The **memcache1** library was generated by Sebastian Thiel, and is placed
under the *MIT* license.
You can read the full text at the repository's [license file][repo-license].