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