aws_sdk_support/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(clippy::deprecated_semver)]
16#![allow(rustdoc::bare_urls)]
17#![allow(rustdoc::redundant_explicit_links)]
18#![allow(rustdoc::invalid_html_tags)]
19#![forbid(unsafe_code)]
20#![warn(missing_docs)]
21#![cfg_attr(docsrs, feature(doc_cfg))]
22//! The _Amazon Web Services Support API Reference_ is intended for programmers who need detailed information about the Amazon Web Services Support operations and data types. You can use the API to manage your support cases programmatically. The Amazon Web Services Support API uses HTTP methods that return results in JSON format.
23//!
24//! You can also use the Amazon Web Services Support API to access features for [Trusted Advisor](http://aws.amazon.com/premiumsupport/trustedadvisor/). You can return a list of checks and their descriptions, get check results, specify checks to refresh, and get the refresh status of checks.
25//!
26//! You can manage your support cases with the following Amazon Web Services Support API operations:
27//! - The CreateCase, DescribeCases, DescribeAttachment, and ResolveCase operations create Amazon Web Services Support cases, retrieve information about cases, and resolve cases.
28//! - The DescribeCommunications, AddCommunicationToCase, and AddAttachmentsToSet operations retrieve and add communications and attachments to Amazon Web Services Support cases.
29//! - The DescribeServices and DescribeSeverityLevels operations return Amazon Web Services service names, service codes, service categories, and problem severity levels. You use these values when you call the CreateCase operation.
30//!
31//! You can also use the Amazon Web Services Support API to call the Trusted Advisor operations. For more information, see [Trusted Advisor](https://docs.aws.amazon.com/awssupport/latest/user/trusted-advisor.html) in the _Amazon Web Services Support User Guide_.
32//!
33//! For authentication of requests, Amazon Web Services Support uses [Signature Version 4 Signing Process](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html).
34//!
35//! For more information about this service and the endpoints to use, see [About the Amazon Web Services Support API](https://docs.aws.amazon.com/awssupport/latest/user/about-support-api.html) in the _Amazon Web Services Support User Guide_.
36//!
37//! ## Getting Started
38//!
39//! > Examples are available for many services and operations, check out the
40//! > [usage examples](https://github.com/awsdocs/aws-doc-sdk-examples/tree/main/rustv1).
41//!
42//! The SDK provides one crate per AWS service. You must add [Tokio](https://crates.io/crates/tokio)
43//! as a dependency within your Rust project to execute asynchronous code. To add `aws-sdk-support` to
44//! your project, add the following to your **Cargo.toml** file:
45//!
46//! ```toml
47//! [dependencies]
48//! aws-config = { version = "1.1.7", features = ["behavior-version-latest"] }
49//! aws-sdk-support = "1.87.0"
50//! tokio = { version = "1", features = ["full"] }
51//! ```
52//!
53//! Then in code, a client can be created with the following:
54//!
55//! ```rust,no_run
56//! use aws_sdk_support as support;
57//!
58//! #[::tokio::main]
59//! async fn main() -> Result<(), support::Error> {
60//! let config = aws_config::load_from_env().await;
61//! let client = aws_sdk_support::Client::new(&config);
62//!
63//! // ... make some calls with the client
64//!
65//! Ok(())
66//! }
67//! ```
68//!
69//! See the [client documentation](https://docs.rs/aws-sdk-support/latest/aws_sdk_support/client/struct.Client.html)
70//! for information on what calls can be made, and the inputs and outputs for each of those calls.
71//!
72//! ## Using the SDK
73//!
74//! Until the SDK is released, we will be adding information about using the SDK to the
75//! [Developer Guide](https://docs.aws.amazon.com/sdk-for-rust/latest/dg/welcome.html). Feel free to suggest
76//! additional sections for the guide by opening an issue and describing what you are trying to do.
77//!
78//! ## Getting Help
79//!
80//! * [GitHub discussions](https://github.com/awslabs/aws-sdk-rust/discussions) - For ideas, RFCs & general questions
81//! * [GitHub issues](https://github.com/awslabs/aws-sdk-rust/issues/new/choose) - For bug reports & feature requests
82//! * [Generated Docs (latest version)](https://awslabs.github.io/aws-sdk-rust/)
83//! * [Usage examples](https://github.com/awsdocs/aws-doc-sdk-examples/tree/main/rustv1)
84//!
85//!
86//! # Crate Organization
87//!
88//! The entry point for most customers will be [`Client`], which exposes one method for each API
89//! offered by AWS Support. The return value of each of these methods is a "fluent builder",
90//! where the different inputs for that API are added by builder-style function call chaining,
91//! followed by calling `send()` to get a [`Future`](std::future::Future) that will result in
92//! either a successful output or a [`SdkError`](crate::error::SdkError).
93//!
94//! Some of these API inputs may be structs or enums to provide more complex structured information.
95//! These structs and enums live in [`types`](crate::types). There are some simpler types for
96//! representing data such as date times or binary blobs that live in [`primitives`](crate::primitives).
97//!
98//! All types required to configure a client via the [`Config`](crate::Config) struct live
99//! in [`config`](crate::config).
100//!
101//! The [`operation`](crate::operation) module has a submodule for every API, and in each submodule
102//! is the input, output, and error type for that API, as well as builders to construct each of those.
103//!
104//! There is a top-level [`Error`](crate::Error) type that encompasses all the errors that the
105//! client can return. Any other error type can be converted to this `Error` type via the
106//! [`From`](std::convert::From) trait.
107//!
108//! The other modules within this crate are not required for normal usage.
109
110// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
111pub use error_meta::Error;
112
113#[doc(inline)]
114pub use config::Config;
115
116/// Client for calling AWS Support.
117/// ## Constructing a `Client`
118///
119/// A [`Config`] is required to construct a client. For most use cases, the [`aws-config`]
120/// crate should be used to automatically resolve this config using
121/// [`aws_config::load_from_env()`], since this will resolve an [`SdkConfig`] which can be shared
122/// across multiple different AWS SDK clients. This config resolution process can be customized
123/// by calling [`aws_config::from_env()`] instead, which returns a [`ConfigLoader`] that uses
124/// the [builder pattern] to customize the default config.
125///
126/// In the simplest case, creating a client looks as follows:
127/// ```rust,no_run
128/// # async fn wrapper() {
129/// let config = aws_config::load_from_env().await;
130/// let client = aws_sdk_support::Client::new(&config);
131/// # }
132/// ```
133///
134/// Occasionally, SDKs may have additional service-specific values that can be set on the [`Config`] that
135/// is absent from [`SdkConfig`], or slightly different settings for a specific client may be desired.
136/// The [`Builder`](crate::config::Builder) struct implements `From<&SdkConfig>`, so setting these specific settings can be
137/// done as follows:
138///
139/// ```rust,no_run
140/// # async fn wrapper() {
141/// let sdk_config = ::aws_config::load_from_env().await;
142/// let config = aws_sdk_support::config::Builder::from(&sdk_config)
143/// # /*
144/// .some_service_specific_setting("value")
145/// # */
146/// .build();
147/// # }
148/// ```
149///
150/// See the [`aws-config` docs] and [`Config`] for more information on customizing configuration.
151///
152/// _Note:_ Client construction is expensive due to connection thread pool initialization, and should
153/// be done once at application start-up.
154///
155/// [`Config`]: crate::Config
156/// [`ConfigLoader`]: https://docs.rs/aws-config/*/aws_config/struct.ConfigLoader.html
157/// [`SdkConfig`]: https://docs.rs/aws-config/*/aws_config/struct.SdkConfig.html
158/// [`aws-config` docs]: https://docs.rs/aws-config/*
159/// [`aws-config`]: https://crates.io/crates/aws-config
160/// [`aws_config::from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.from_env.html
161/// [`aws_config::load_from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.load_from_env.html
162/// [builder pattern]: https://rust-lang.github.io/api-guidelines/type-safety.html#builders-enable-construction-of-complex-values-c-builder
163/// # Using the `Client`
164///
165/// A client has a function for every operation that can be performed by the service.
166/// For example, the [`AddAttachmentsToSet`](crate::operation::add_attachments_to_set) operation has
167/// a [`Client::add_attachments_to_set`], function which returns a builder for that operation.
168/// The fluent builder ultimately has a `send()` function that returns an async future that
169/// returns a result, as illustrated below:
170///
171/// ```rust,ignore
172/// let result = client.add_attachments_to_set()
173/// .attachment_set_id("example")
174/// .send()
175/// .await;
176/// ```
177///
178/// The underlying HTTP requests that get made by this can be modified with the `customize_operation`
179/// function on the fluent builder. See the [`customize`](crate::client::customize) module for more
180/// information.
181pub mod client;
182
183/// Configuration for AWS Support.
184pub mod config;
185
186/// Common errors and error handling utilities.
187pub mod error;
188
189mod error_meta;
190
191/// Information about this crate.
192pub mod meta;
193
194/// All operations that this crate can perform.
195pub mod operation;
196
197/// Primitives such as `Blob` or `DateTime` used by other types.
198pub mod primitives;
199
200/// Data structures used by operation inputs/outputs.
201pub mod types;
202
203pub(crate) mod protocol_serde;
204
205mod sdk_feature_tracker;
206
207mod serialization_settings;
208
209mod endpoint_lib;
210
211mod lens;
212
213mod serde_util;
214
215mod json_errors;
216
217#[doc(inline)]
218pub use client::Client;