google_cloudprofiler2/
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 Profiler* crate version *7.0.0+20251006*, where *20251006* is the exact revision of the *cloudprofiler:v2* schema built by the [mako](http://www.makotemplates.org/) code generator *v7.0.0*.
6//!
7//! Everything else about the *Cloud Profiler* *v2* API can be found at the
8//! [official documentation site](https://cloud.google.com/profiler/).
9//! The original source code is [on github](https://github.com/Byron/google-apis-rs/tree/main/gen/cloudprofiler2).
10//! # Features
11//!
12//! Handle the following *Resources* with ease from the central [hub](CloudProfiler) ...
13//!
14//! * projects
15//!  * [*profiles create*](api::ProjectProfileCreateCall), [*profiles create offline*](api::ProjectProfileCreateOfflineCall), [*profiles list*](api::ProjectProfileListCall) and [*profiles patch*](api::ProjectProfilePatchCall)
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](CloudProfiler)**
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().profiles_create(...).doit().await
51//! let r = hub.projects().profiles_create_offline(...).doit().await
52//! let r = hub.projects().profiles_patch(...).doit().await
53//! ```
54//!
55//! The `resource()` and `activity(...)` calls create [builders][builder-pattern]. The second one dealing with `Activities`
56//! supports various methods to configure the impending operation (not shown here). It is made such that all required arguments have to be
57//! specified right away (i.e. `(...)`), whereas all optional ones can be [build up][builder-pattern] as desired.
58//! The `doit()` method performs the actual communication with the server and returns the respective result.
59//!
60//! # Usage
61//!
62//! ## Setting up your Project
63//!
64//! To use this library, you would put the following lines into your `Cargo.toml` file:
65//!
66//! ```toml
67//! [dependencies]
68//! google-cloudprofiler2 = "*"
69//! serde = "1"
70//! serde_json = "1"
71//! ```
72//!
73//! ## A complete example
74//!
75//! ```test_harness,no_run
76//! extern crate hyper;
77//! extern crate hyper_rustls;
78//! extern crate google_cloudprofiler2 as cloudprofiler2;
79//! use cloudprofiler2::api::Profile;
80//! use cloudprofiler2::{Result, Error};
81//! # async fn dox() {
82//! use cloudprofiler2::{CloudProfiler, FieldMask, hyper_rustls, hyper_util, yup_oauth2};
83//!
84//! // Get an ApplicationSecret instance by some means. It contains the `client_id` and
85//! // `client_secret`, among other things.
86//! let secret: yup_oauth2::ApplicationSecret = Default::default();
87//! // Instantiate the authenticator. It will choose a suitable authentication flow for you,
88//! // unless you replace  `None` with the desired Flow.
89//! // Provide your own `AuthenticatorDelegate` to adjust the way it operates and get feedback about
90//! // what's going on. You probably want to bring in your own `TokenStorage` to persist tokens and
91//! // retrieve them from storage.
92//! let connector = hyper_rustls::HttpsConnectorBuilder::new()
93//!     .with_native_roots()
94//!     .unwrap()
95//!     .https_only()
96//!     .enable_http2()
97//!     .build();
98//!
99//! let executor = hyper_util::rt::TokioExecutor::new();
100//! let auth = yup_oauth2::InstalledFlowAuthenticator::with_client(
101//!     secret,
102//!     yup_oauth2::InstalledFlowReturnMethod::HTTPRedirect,
103//!     yup_oauth2::client::CustomHyperClientBuilder::from(
104//!         hyper_util::client::legacy::Client::builder(executor).build(connector),
105//!     ),
106//! ).build().await.unwrap();
107//!
108//! let client = hyper_util::client::legacy::Client::builder(
109//!     hyper_util::rt::TokioExecutor::new()
110//! )
111//! .build(
112//!     hyper_rustls::HttpsConnectorBuilder::new()
113//!         .with_native_roots()
114//!         .unwrap()
115//!         .https_or_http()
116//!         .enable_http2()
117//!         .build()
118//! );
119//! let mut hub = CloudProfiler::new(client, auth);
120//! // As the method needs a request, you would usually fill it with the desired information
121//! // into the respective structure. Some of the parts shown here might not be applicable !
122//! // Values shown here are possibly random and not representative !
123//! let mut req = Profile::default();
124//!
125//! // You can configure optional parameters by calling the respective setters at will, and
126//! // execute the final call using `doit()`.
127//! // Values shown here are possibly random and not representative !
128//! let result = hub.projects().profiles_patch(req, "name")
129//!              .update_mask(FieldMask::new::<&str>(&[]))
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::CloudProfiler;