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