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