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