google_datastore1/lib.rs
1// DO NOT EDIT !
2// This file was generated automatically from 'src/generator/templates/api/lib.rs.mako'
3// DO NOT EDIT !
4
5//! This documentation was generated from *datastore* crate version *6.0.0+20240617*, where *20240617* is the exact revision of the *datastore:v1* schema built by the [mako](http://www.makotemplates.org/) code generator *v6.0.0*.
6//!
7//! Everything else about the *datastore* *v1* API can be found at the
8//! [official documentation site](https://cloud.google.com/datastore/).
9//! The original source code is [on github](https://github.com/Byron/google-apis-rs/tree/main/gen/datastore1).
10//! # Features
11//!
12//! Handle the following *Resources* with ease from the central [hub](Datastore) ...
13//!
14//! * projects
15//! * [*allocate ids*](api::ProjectAllocateIdCall), [*begin transaction*](api::ProjectBeginTransactionCall), [*commit*](api::ProjectCommitCall), [*export*](api::ProjectExportCall), [*import*](api::ProjectImportCall), [*indexes create*](api::ProjectIndexCreateCall), [*indexes delete*](api::ProjectIndexDeleteCall), [*indexes get*](api::ProjectIndexGetCall), [*indexes list*](api::ProjectIndexListCall), [*lookup*](api::ProjectLookupCall), [*operations cancel*](api::ProjectOperationCancelCall), [*operations delete*](api::ProjectOperationDeleteCall), [*operations get*](api::ProjectOperationGetCall), [*operations list*](api::ProjectOperationListCall), [*reserve ids*](api::ProjectReserveIdCall), [*rollback*](api::ProjectRollbackCall), [*run aggregation query*](api::ProjectRunAggregationQueryCall) and [*run query*](api::ProjectRunQueryCall)
16//!
17//!
18//!
19//!
20//! Not what you are looking for ? Find all other Google APIs in their Rust [documentation index](http://byron.github.io/google-apis-rs).
21//!
22//! # Structure of this Library
23//!
24//! The API is structured into the following primary items:
25//!
26//! * **[Hub](Datastore)**
27//! * a central object to maintain state and allow accessing all *Activities*
28//! * creates [*Method Builders*](common::MethodsBuilder) which in turn
29//! allow access to individual [*Call Builders*](common::CallBuilder)
30//! * **[Resources](common::Resource)**
31//! * primary types that you can apply *Activities* to
32//! * a collection of properties and *Parts*
33//! * **[Parts](common::Part)**
34//! * a collection of properties
35//! * never directly used in *Activities*
36//! * **[Activities](common::CallBuilder)**
37//! * operations to apply to *Resources*
38//!
39//! All *structures* are marked with applicable traits to further categorize them and ease browsing.
40//!
41//! Generally speaking, you can invoke *Activities* like this:
42//!
43//! ```Rust,ignore
44//! let r = hub.resource().activity(...).doit().await
45//! ```
46//!
47//! Or specifically ...
48//!
49//! ```ignore
50//! let r = hub.projects().indexes_create(...).doit().await
51//! let r = hub.projects().indexes_delete(...).doit().await
52//! let r = hub.projects().operations_get(...).doit().await
53//! let r = hub.projects().export(...).doit().await
54//! let r = hub.projects().import(...).doit().await
55//! ```
56//!
57//! The `resource()` and `activity(...)` calls create [builders][builder-pattern]. The second one dealing with `Activities`
58//! supports various methods to configure the impending operation (not shown here). It is made such that all required arguments have to be
59//! specified right away (i.e. `(...)`), whereas all optional ones can be [build up][builder-pattern] as desired.
60//! The `doit()` method performs the actual communication with the server and returns the respective result.
61//!
62//! # Usage
63//!
64//! ## Setting up your Project
65//!
66//! To use this library, you would put the following lines into your `Cargo.toml` file:
67//!
68//! ```toml
69//! [dependencies]
70//! google-datastore1 = "*"
71//! serde = "1"
72//! serde_json = "1"
73//! ```
74//!
75//! ## A complete example
76//!
77//! ```test_harness,no_run
78//! extern crate hyper;
79//! extern crate hyper_rustls;
80//! extern crate google_datastore1 as datastore1;
81//! use datastore1::api::GoogleDatastoreAdminV1Index;
82//! use datastore1::{Result, Error};
83//! # async fn dox() {
84//! use datastore1::{Datastore, FieldMask, hyper_rustls, hyper_util, yup_oauth2};
85//!
86//! // Get an ApplicationSecret instance by some means. It contains the `client_id` and
87//! // `client_secret`, among other things.
88//! let secret: yup_oauth2::ApplicationSecret = Default::default();
89//! // Instantiate the authenticator. It will choose a suitable authentication flow for you,
90//! // unless you replace `None` with the desired Flow.
91//! // Provide your own `AuthenticatorDelegate` to adjust the way it operates and get feedback about
92//! // what's going on. You probably want to bring in your own `TokenStorage` to persist tokens and
93//! // retrieve them from storage.
94//! let auth = yup_oauth2::InstalledFlowAuthenticator::builder(
95//! secret,
96//! yup_oauth2::InstalledFlowReturnMethod::HTTPRedirect,
97//! ).build().await.unwrap();
98//!
99//! let client = hyper_util::client::legacy::Client::builder(
100//! hyper_util::rt::TokioExecutor::new()
101//! )
102//! .build(
103//! hyper_rustls::HttpsConnectorBuilder::new()
104//! .with_native_roots()
105//! .unwrap()
106//! .https_or_http()
107//! .enable_http1()
108//! .build()
109//! );
110//! let mut hub = Datastore::new(client, auth);
111//! // As the method needs a request, you would usually fill it with the desired information
112//! // into the respective structure. Some of the parts shown here might not be applicable !
113//! // Values shown here are possibly random and not representative !
114//! let mut req = GoogleDatastoreAdminV1Index::default();
115//!
116//! // You can configure optional parameters by calling the respective setters at will, and
117//! // execute the final call using `doit()`.
118//! // Values shown here are possibly random and not representative !
119//! let result = hub.projects().indexes_create(req, "projectId")
120//! .doit().await;
121//!
122//! match result {
123//! Err(e) => match e {
124//! // The Error enum provides details about what exactly happened.
125//! // You can also just use its `Debug`, `Display` or `Error` traits
126//! Error::HttpError(_)
127//! |Error::Io(_)
128//! |Error::MissingAPIKey
129//! |Error::MissingToken(_)
130//! |Error::Cancelled
131//! |Error::UploadSizeLimitExceeded(_, _)
132//! |Error::Failure(_)
133//! |Error::BadRequest(_)
134//! |Error::FieldClash(_)
135//! |Error::JsonDecodeError(_, _) => println!("{}", e),
136//! },
137//! Ok(res) => println!("Success: {:?}", res),
138//! }
139//! # }
140//! ```
141//! ## Handling Errors
142//!
143//! All errors produced by the system are provided either as [Result](common::Result) enumeration as return value of
144//! the doit() methods, or handed as possibly intermediate results to either the
145//! [Hub Delegate](common::Delegate), or the [Authenticator Delegate](https://docs.rs/yup-oauth2/*/yup_oauth2/trait.AuthenticatorDelegate.html).
146//!
147//! When delegates handle errors or intermediate values, they may have a chance to instruct the system to retry. This
148//! makes the system potentially resilient to all kinds of errors.
149//!
150//! ## Uploads and Downloads
151//! If a method supports downloads, the response body, which is part of the [Result](common::Result), should be
152//! read by you to obtain the media.
153//! If such a method also supports a [Response Result](common::ResponseResult), it will return that by default.
154//! 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
155//! this call: `.param("alt", "media")`.
156//!
157//! Methods supporting uploads can do so using up to 2 different protocols:
158//! *simple* and *resumable*. The distinctiveness of each is represented by customized
159//! `doit(...)` methods, which are then named `upload(...)` and `upload_resumable(...)` respectively.
160//!
161//! ## Customization and Callbacks
162//!
163//! You may alter the way an `doit()` method is called by providing a [delegate](common::Delegate) to the
164//! [Method Builder](common::CallBuilder) before making the final `doit()` call.
165//! Respective methods will be called to provide progress information, as well as determine whether the system should
166//! retry on failure.
167//!
168//! The [delegate trait](common::Delegate) is default-implemented, allowing you to customize it with minimal effort.
169//!
170//! ## Optional Parts in Server-Requests
171//!
172//! All structures provided by this library are made to be [encodable](common::RequestValue) and
173//! [decodable](common::ResponseResult) via *json*. Optionals are used to indicate that partial requests are responses
174//! are valid.
175//! Most optionals are are considered [Parts](common::Part) which are identifiable by name, which will be sent to
176//! the server to indicate either the set parts of the request or the desired parts in the response.
177//!
178//! ## Builder Arguments
179//!
180//! Using [method builders](common::CallBuilder), you are able to prepare an action call by repeatedly calling it's methods.
181//! These will always take a single argument, for which the following statements are true.
182//!
183//! * [PODs][wiki-pod] are handed by copy
184//! * strings are passed as `&str`
185//! * [request values](common::RequestValue) are moved
186//!
187//! Arguments will always be copied or cloned into the builder, to make them independent of their original life times.
188//!
189//! [wiki-pod]: http://en.wikipedia.org/wiki/Plain_old_data_structure
190//! [builder-pattern]: http://en.wikipedia.org/wiki/Builder_pattern
191//! [google-go-api]: https://github.com/google/google-api-go-client
192//!
193//! ## Cargo Features
194//!
195//! * `utoipa` - Add support for [utoipa](https://crates.io/crates/utoipa) and derive `utoipa::ToSchema` on all
196//! the types. You'll have to import and register the required types in `#[openapi(schemas(...))]`, otherwise the
197//! generated `openapi` spec would be invalid.
198//!
199//!
200//!
201
202// Unused attributes happen thanks to defined, but unused structures We don't
203// warn about this, as depending on the API, some data structures or facilities
204// are never used. Instead of pre-determining this, we just disable the lint.
205// It's manually tuned to not have any unused imports in fully featured APIs.
206// Same with unused_mut.
207#![allow(unused_imports, unused_mut, dead_code)]
208
209// DO NOT EDIT !
210// This file was generated automatically from 'src/generator/templates/api/lib.rs.mako'
211// DO NOT EDIT !
212
213pub extern crate hyper;
214pub extern crate hyper_rustls;
215pub extern crate hyper_util;
216#[cfg(feature = "yup-oauth2")]
217pub extern crate yup_oauth2;
218
219pub extern crate google_apis_common as common;
220pub use common::{Delegate, Error, FieldMask, Result};
221
222pub mod api;
223pub use api::Datastore;