OMGeeky/google-apis-rs
1
0
Fork 0
mirror of https://github.com/OMGeeky/google-apis-rs.git synced 2026-02-23 15:49:49 +01:00
Code Issues Packages Projects Releases Wiki Activity

make regen-apis

Browse Source
This commit is contained in:
OMGeeky
2023-10-21 02:11:31 +02:00
parent ce47a46ca4
commit 90ac61067f
356 changed files with 5261 additions and 5261 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
gen/securitycenter1/src/lib.rs
View File

@@ -9,7 +9,7 @@
//! The original source code is [on github](https://github.com/Byron/google-apis-rs/tree/main/gen/securitycenter1).
//! # Features
//!
//! Handle the following *Resources* with ease from the central [hub](SecurityCommandCenter) ...
//! Handle the following *Resources* with ease from the central [hub](SecurityCommandCenter) ...
//!
//! * [folders](api::Folder)
//! * [*assets group*](api::FolderAssetGroupCall), [*assets list*](api::FolderAssetListCall), [*assets update security marks*](api::FolderAssetUpdateSecurityMarkCall), [*big query exports create*](api::FolderBigQueryExportCreateCall), [*big query exports delete*](api::FolderBigQueryExportDeleteCall), [*big query exports get*](api::FolderBigQueryExportGetCall), [*big query exports list*](api::FolderBigQueryExportListCall), [*big query exports patch*](api::FolderBigQueryExportPatchCall), [*event threat detection settings custom modules create*](api::FolderEventThreatDetectionSettingCustomModuleCreateCall), [*event threat detection settings custom modules delete*](api::FolderEventThreatDetectionSettingCustomModuleDeleteCall), [*event threat detection settings custom modules get*](api::FolderEventThreatDetectionSettingCustomModuleGetCall), [*event threat detection settings custom modules list*](api::FolderEventThreatDetectionSettingCustomModuleListCall), [*event threat detection settings custom modules list descendant*](api::FolderEventThreatDetectionSettingCustomModuleListDescendantCall), [*event threat detection settings custom modules patch*](api::FolderEventThreatDetectionSettingCustomModulePatchCall), [*event threat detection settings effective custom modules get*](api::FolderEventThreatDetectionSettingEffectiveCustomModuleGetCall), [*event threat detection settings effective custom modules list*](api::FolderEventThreatDetectionSettingEffectiveCustomModuleListCall), [*event threat detection settings validate custom module*](api::FolderEventThreatDetectionSettingValidateCustomModuleCall), [*findings bulk mute*](api::FolderFindingBulkMuteCall), [*locations mute configs delete*](api::FolderLocationMuteConfigDeleteCall), [*locations mute configs get*](api::FolderLocationMuteConfigGetCall), [*locations mute configs patch*](api::FolderLocationMuteConfigPatchCall), [*mute configs create*](api::FolderMuteConfigCreateCall), [*mute configs delete*](api::FolderMuteConfigDeleteCall), [*mute configs get*](api::FolderMuteConfigGetCall), [*mute configs list*](api::FolderMuteConfigListCall), [*mute configs patch*](api::FolderMuteConfigPatchCall), [*notification configs create*](api::FolderNotificationConfigCreateCall), [*notification configs delete*](api::FolderNotificationConfigDeleteCall), [*notification configs get*](api::FolderNotificationConfigGetCall), [*notification configs list*](api::FolderNotificationConfigListCall), [*notification configs patch*](api::FolderNotificationConfigPatchCall), [*security health analytics settings custom modules create*](api::FolderSecurityHealthAnalyticsSettingCustomModuleCreateCall), [*security health analytics settings custom modules delete*](api::FolderSecurityHealthAnalyticsSettingCustomModuleDeleteCall), [*security health analytics settings custom modules get*](api::FolderSecurityHealthAnalyticsSettingCustomModuleGetCall), [*security health analytics settings custom modules list*](api::FolderSecurityHealthAnalyticsSettingCustomModuleListCall), [*security health analytics settings custom modules list descendant*](api::FolderSecurityHealthAnalyticsSettingCustomModuleListDescendantCall), [*security health analytics settings custom modules patch*](api::FolderSecurityHealthAnalyticsSettingCustomModulePatchCall), [*security health analytics settings custom modules simulate*](api::FolderSecurityHealthAnalyticsSettingCustomModuleSimulateCall), [*security health analytics settings effective custom modules get*](api::FolderSecurityHealthAnalyticsSettingEffectiveCustomModuleGetCall), [*security health analytics settings effective custom modules list*](api::FolderSecurityHealthAnalyticsSettingEffectiveCustomModuleListCall), [*sources findings external systems patch*](api::FolderSourceFindingExternalSystemPatchCall), [*sources findings group*](api::FolderSourceFindingGroupCall), [*sources findings list*](api::FolderSourceFindingListCall), [*sources findings patch*](api::FolderSourceFindingPatchCall), [*sources findings set mute*](api::FolderSourceFindingSetMuteCall), [*sources findings set state*](api::FolderSourceFindingSetStateCall), [*sources findings update security marks*](api::FolderSourceFindingUpdateSecurityMarkCall) and [*sources list*](api::FolderSourceListCall)
@@ -101,8 +101,8 @@
//! let r = hub.folders().sources_list(...).doit().await
//! ```
//!
//! The `resource()` and `activity(...)` calls create [builders][builder-pattern]. The second one dealing with `Activities`
//! supports various methods to configure the impending operation (not shown here). It is made such that all required arguments have to be
//! The `resource()` and `activity(...)` calls create [builders][builder-pattern]. The second one dealing with `Activities`
//! supports various methods to configure the impending operation (not shown here). It is made such that all required arguments have to be
//! specified right away (i.e. `(...)`), whereas all optional ones can be [build up][builder-pattern] as desired.
//! The `doit()` method performs the actual communication with the server and returns the respective result.
//!
@@ -130,12 +130,12 @@
//! use std::default::Default;
//! use securitycenter1::{SecurityCommandCenter, oauth2, hyper, hyper_rustls, chrono, FieldMask};
//!
//! // Get an ApplicationSecret instance by some means. It contains the `client_id` and
//! // Get an ApplicationSecret instance by some means. It contains the `client_id` and
//! // `client_secret`, among other things.
//! let secret: oauth2::ApplicationSecret = Default::default();
//! // Instantiate the authenticator. It will choose a suitable authentication flow for you,
//! // Instantiate the authenticator. It will choose a suitable authentication flow for you,
//! // unless you replace `None` with the desired Flow.
//! // Provide your own `AuthenticatorDelegate` to adjust the way it operates and get feedback about
//! // Provide your own `AuthenticatorDelegate` to adjust the way it operates and get feedback about
//! // what's going on. You probably want to bring in your own `TokenStorage` to persist tokens and
//! // retrieve them from storage.
//! let auth = oauth2::InstalledFlowAuthenticator::builder(
@@ -178,10 +178,10 @@
//! ## Handling Errors
//!
//! All errors produced by the system are provided either as [Result](client::Result) enumeration as return value of
//! the doit() methods, or handed as possibly intermediate results to either the
//! the doit() methods, or handed as possibly intermediate results to either the
//! [Hub Delegate](client::Delegate), or the [Authenticator Delegate](https://docs.rs/yup-oauth2/*/yup_oauth2/trait.AuthenticatorDelegate.html).
//!
//! When delegates handle errors or intermediate values, they may have a chance to instruct the system to retry. This
//! When delegates handle errors or intermediate values, they may have a chance to instruct the system to retry. This
//! makes the system potentially resilient to all kinds of errors.
//!
//! ## Uploads and Downloads
@@ -191,25 +191,25 @@
//! 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
//! this call: `.param("alt", "media")`.
//!
//! Methods supporting uploads can do so using up to 2 different protocols:
//! *simple* and *resumable*. The distinctiveness of each is represented by customized
//! Methods supporting uploads can do so using up to 2 different protocols:
//! *simple* and *resumable*. The distinctiveness of each is represented by customized
//! `doit(...)` methods, which are then named `upload(...)` and `upload_resumable(...)` respectively.
//!
//! ## Customization and Callbacks
//!
//! You may alter the way an `doit()` method is called by providing a [delegate](client::Delegate) to the
//! [Method Builder](client::CallBuilder) before making the final `doit()` call.
//! Respective methods will be called to provide progress information, as well as determine whether the system should
//! You may alter the way an `doit()` method is called by providing a [delegate](client::Delegate) to the
//! [Method Builder](client::CallBuilder) before making the final `doit()` call.
//! Respective methods will be called to provide progress information, as well as determine whether the system should
//! retry on failure.
//!
//! The [delegate trait](client::Delegate) is default-implemented, allowing you to customize it with minimal effort.
//!
//! ## Optional Parts in Server-Requests
//!
//! All structures provided by this library are made to be [encodable](client::RequestValue) and
//! [decodable](client::ResponseResult) via *json*. Optionals are used to indicate that partial requests are responses
//! All structures provided by this library are made to be [encodable](client::RequestValue) and
//! [decodable](client::ResponseResult) via *json*. Optionals are used to indicate that partial requests are responses
//! are valid.
//! Most optionals are are considered [Parts](client::Part) which are identifiable by name, which will be sent to
//! Most optionals are are considered [Parts](client::Part) which are identifiable by name, which will be sent to
//! the server to indicate either the set parts of the request or the desired parts in the response.
//!
//! ## Builder Arguments