aws_sdk_codestarnotifications/lib.rs
1#![allow(deprecated)]
2#![allow(unknown_lints)]
3#![allow(clippy::module_inception)]
4#![allow(clippy::upper_case_acronyms)]
5#![allow(clippy::large_enum_variant)]
6#![allow(clippy::wrong_self_convention)]
7#![allow(clippy::should_implement_trait)]
8#![allow(clippy::disallowed_names)]
9#![allow(clippy::vec_init_then_push)]
10#![allow(clippy::type_complexity)]
11#![allow(clippy::needless_return)]
12#![allow(clippy::derive_partial_eq_without_eq)]
13#![allow(clippy::result_large_err)]
14#![allow(clippy::unnecessary_map_on_constructor)]
15#![allow(rustdoc::bare_urls)]
16#![allow(rustdoc::redundant_explicit_links)]
17#![allow(rustdoc::invalid_html_tags)]
18#![forbid(unsafe_code)]
19#![warn(missing_docs)]
20#![cfg_attr(docsrs, feature(doc_auto_cfg))]
21//! This AWS CodeStar Notifications API Reference provides descriptions and usage examples of the operations and data types for the AWS CodeStar Notifications API. You can use the AWS CodeStar Notifications API to work with the following objects:
22//!
23//! Notification rules, by calling the following:
24//! - CreateNotificationRule, which creates a notification rule for a resource in your account.
25//! - DeleteNotificationRule, which deletes a notification rule.
26//! - DescribeNotificationRule, which provides information about a notification rule.
27//! - ListNotificationRules, which lists the notification rules associated with your account.
28//! - UpdateNotificationRule, which changes the name, events, or targets associated with a notification rule.
29//! - Subscribe, which subscribes a target to a notification rule.
30//! - Unsubscribe, which removes a target from a notification rule.
31//!
32//! Targets, by calling the following:
33//! - DeleteTarget, which removes a notification rule target from a notification rule.
34//! - ListTargets, which lists the targets associated with a notification rule.
35//!
36//! Events, by calling the following:
37//! - ListEventTypes, which lists the event types you can include in a notification rule.
38//!
39//! Tags, by calling the following:
40//! - ListTagsForResource, which lists the tags already associated with a notification rule in your account.
41//! - TagResource, which associates a tag you provide with a notification rule in your account.
42//! - UntagResource, which removes a tag from a notification rule in your account.
43//!
44//! For information about how to use AWS CodeStar Notifications, see the [Amazon Web Services Developer Tools Console User Guide](https://docs.aws.amazon.com/dtconsole/latest/userguide/what-is-dtconsole.html).
45//!
46//! ## Getting Started
47//!
48//! > Examples are available for many services and operations, check out the
49//! > [examples folder in GitHub](https://github.com/awslabs/aws-sdk-rust/tree/main/examples).
50//!
51//! The SDK provides one crate per AWS service. You must add [Tokio](https://crates.io/crates/tokio)
52//! as a dependency within your Rust project to execute asynchronous code. To add `aws-sdk-codestarnotifications` to
53//! your project, add the following to your **Cargo.toml** file:
54//!
55//! ```toml
56//! [dependencies]
57//! aws-config = { version = "1.1.7", features = ["behavior-version-latest"] }
58//! aws-sdk-codestarnotifications = "1.73.0"
59//! tokio = { version = "1", features = ["full"] }
60//! ```
61//!
62//! Then in code, a client can be created with the following:
63//!
64//! ```rust,no_run
65//! use aws_sdk_codestarnotifications as codestarnotifications;
66//!
67//! #[::tokio::main]
68//! async fn main() -> Result<(), codestarnotifications::Error> {
69//! let config = aws_config::load_from_env().await;
70//! let client = aws_sdk_codestarnotifications::Client::new(&config);
71//!
72//! // ... make some calls with the client
73//!
74//! Ok(())
75//! }
76//! ```
77//!
78//! See the [client documentation](https://docs.rs/aws-sdk-codestarnotifications/latest/aws_sdk_codestarnotifications/client/struct.Client.html)
79//! for information on what calls can be made, and the inputs and outputs for each of those calls.
80//!
81//! ## Using the SDK
82//!
83//! Until the SDK is released, we will be adding information about using the SDK to the
84//! [Developer Guide](https://docs.aws.amazon.com/sdk-for-rust/latest/dg/welcome.html). Feel free to suggest
85//! additional sections for the guide by opening an issue and describing what you are trying to do.
86//!
87//! ## Getting Help
88//!
89//! * [GitHub discussions](https://github.com/awslabs/aws-sdk-rust/discussions) - For ideas, RFCs & general questions
90//! * [GitHub issues](https://github.com/awslabs/aws-sdk-rust/issues/new/choose) - For bug reports & feature requests
91//! * [Generated Docs (latest version)](https://awslabs.github.io/aws-sdk-rust/)
92//! * [Usage examples](https://github.com/awslabs/aws-sdk-rust/tree/main/examples)
93//!
94//!
95//! # Crate Organization
96//!
97//! The entry point for most customers will be [`Client`], which exposes one method for each API
98//! offered by AWS CodeStar Notifications. The return value of each of these methods is a "fluent builder",
99//! where the different inputs for that API are added by builder-style function call chaining,
100//! followed by calling `send()` to get a [`Future`](std::future::Future) that will result in
101//! either a successful output or a [`SdkError`](crate::error::SdkError).
102//!
103//! Some of these API inputs may be structs or enums to provide more complex structured information.
104//! These structs and enums live in [`types`](crate::types). There are some simpler types for
105//! representing data such as date times or binary blobs that live in [`primitives`](crate::primitives).
106//!
107//! All types required to configure a client via the [`Config`](crate::Config) struct live
108//! in [`config`](crate::config).
109//!
110//! The [`operation`](crate::operation) module has a submodule for every API, and in each submodule
111//! is the input, output, and error type for that API, as well as builders to construct each of those.
112//!
113//! There is a top-level [`Error`](crate::Error) type that encompasses all the errors that the
114//! client can return. Any other error type can be converted to this `Error` type via the
115//! [`From`](std::convert::From) trait.
116//!
117//! The other modules within this crate are not required for normal usage.
118
119// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
120pub use error_meta::Error;
121
122#[doc(inline)]
123pub use config::Config;
124
125/// Client for calling AWS CodeStar Notifications.
126/// ## Constructing a `Client`
127///
128/// A [`Config`] is required to construct a client. For most use cases, the [`aws-config`]
129/// crate should be used to automatically resolve this config using
130/// [`aws_config::load_from_env()`], since this will resolve an [`SdkConfig`] which can be shared
131/// across multiple different AWS SDK clients. This config resolution process can be customized
132/// by calling [`aws_config::from_env()`] instead, which returns a [`ConfigLoader`] that uses
133/// the [builder pattern] to customize the default config.
134///
135/// In the simplest case, creating a client looks as follows:
136/// ```rust,no_run
137/// # async fn wrapper() {
138/// let config = aws_config::load_from_env().await;
139/// let client = aws_sdk_codestarnotifications::Client::new(&config);
140/// # }
141/// ```
142///
143/// Occasionally, SDKs may have additional service-specific values that can be set on the [`Config`] that
144/// is absent from [`SdkConfig`], or slightly different settings for a specific client may be desired.
145/// The [`Builder`](crate::config::Builder) struct implements `From<&SdkConfig>`, so setting these specific settings can be
146/// done as follows:
147///
148/// ```rust,no_run
149/// # async fn wrapper() {
150/// let sdk_config = ::aws_config::load_from_env().await;
151/// let config = aws_sdk_codestarnotifications::config::Builder::from(&sdk_config)
152/// # /*
153/// .some_service_specific_setting("value")
154/// # */
155/// .build();
156/// # }
157/// ```
158///
159/// See the [`aws-config` docs] and [`Config`] for more information on customizing configuration.
160///
161/// _Note:_ Client construction is expensive due to connection thread pool initialization, and should
162/// be done once at application start-up.
163///
164/// [`Config`]: crate::Config
165/// [`ConfigLoader`]: https://docs.rs/aws-config/*/aws_config/struct.ConfigLoader.html
166/// [`SdkConfig`]: https://docs.rs/aws-config/*/aws_config/struct.SdkConfig.html
167/// [`aws-config` docs]: https://docs.rs/aws-config/*
168/// [`aws-config`]: https://crates.io/crates/aws-config
169/// [`aws_config::from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.from_env.html
170/// [`aws_config::load_from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.load_from_env.html
171/// [builder pattern]: https://rust-lang.github.io/api-guidelines/type-safety.html#builders-enable-construction-of-complex-values-c-builder
172/// # Using the `Client`
173///
174/// A client has a function for every operation that can be performed by the service.
175/// For example, the [`CreateNotificationRule`](crate::operation::create_notification_rule) operation has
176/// a [`Client::create_notification_rule`], function which returns a builder for that operation.
177/// The fluent builder ultimately has a `send()` function that returns an async future that
178/// returns a result, as illustrated below:
179///
180/// ```rust,ignore
181/// let result = client.create_notification_rule()
182/// .name("example")
183/// .send()
184/// .await;
185/// ```
186///
187/// The underlying HTTP requests that get made by this can be modified with the `customize_operation`
188/// function on the fluent builder. See the [`customize`](crate::client::customize) module for more
189/// information.
190pub mod client;
191
192/// Configuration for AWS CodeStar Notifications.
193pub mod config;
194
195/// Common errors and error handling utilities.
196pub mod error;
197
198mod error_meta;
199
200/// Information about this crate.
201pub mod meta;
202
203/// All operations that this crate can perform.
204pub mod operation;
205
206/// Primitives such as `Blob` or `DateTime` used by other types.
207pub mod primitives;
208
209/// Data structures used by operation inputs/outputs.
210pub mod types;
211
212mod auth_plugin;
213
214pub(crate) mod client_idempotency_token;
215
216mod idempotency_token;
217
218pub(crate) mod protocol_serde;
219
220mod sdk_feature_tracker;
221
222mod serialization_settings;
223
224mod endpoint_lib;
225
226mod lens;
227
228mod serde_util;
229
230mod json_errors;
231
232#[doc(inline)]
233pub use client::Client;