aws_sdk_dsql/
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//! This is an interface reference for Amazon Aurora DSQL. It contains documentation for one of the programming or command line interfaces you can use to manage Amazon Aurora DSQL.
21//!
22//! Amazon Aurora DSQL is a serverless, distributed SQL database suitable for workloads of any size. Aurora DSQL is available in both single-Region and multi-Region configurations, so your clusters and databases are always available even if an Availability Zone or an Amazon Web Services Region are unavailable. Aurora DSQL lets you focus on using your data to acquire new insights for your business and customers.
23//!
24//! ## Getting Started
25//!
26//! > Examples are available for many services and operations, check out the
27//! > [examples folder in GitHub](https://github.com/awslabs/aws-sdk-rust/tree/main/examples).
28//!
29//! The SDK provides one crate per AWS service. You must add [Tokio](https://crates.io/crates/tokio)
30//! as a dependency within your Rust project to execute asynchronous code. To add `aws-sdk-dsql` to
31//! your project, add the following to your **Cargo.toml** file:
32//!
33//! ```toml
34//! [dependencies]
35//! aws-config = { version = "1.1.7", features = ["behavior-version-latest"] }
36//! aws-sdk-dsql = "1.13.0"
37//! tokio = { version = "1", features = ["full"] }
38//! ```
39//!
40//! Then in code, a client can be created with the following:
41//!
42//! ```rust,no_run
43//! use aws_sdk_dsql as dsql;
44//!
45//! #[::tokio::main]
46//! async fn main() -> Result<(), dsql::Error> {
47//!     let config = aws_config::load_from_env().await;
48//!     let client = aws_sdk_dsql::Client::new(&config);
49//!
50//!     // ... make some calls with the client
51//!
52//!     Ok(())
53//! }
54//! ```
55//!
56//! See the [client documentation](https://docs.rs/aws-sdk-dsql/latest/aws_sdk_dsql/client/struct.Client.html)
57//! for information on what calls can be made, and the inputs and outputs for each of those calls.
58//!
59//! ## Using the SDK
60//!
61//! Until the SDK is released, we will be adding information about using the SDK to the
62//! [Developer Guide](https://docs.aws.amazon.com/sdk-for-rust/latest/dg/welcome.html). Feel free to suggest
63//! additional sections for the guide by opening an issue and describing what you are trying to do.
64//!
65//! ## Getting Help
66//!
67//! * [GitHub discussions](https://github.com/awslabs/aws-sdk-rust/discussions) - For ideas, RFCs & general questions
68//! * [GitHub issues](https://github.com/awslabs/aws-sdk-rust/issues/new/choose) - For bug reports & feature requests
69//! * [Generated Docs (latest version)](https://awslabs.github.io/aws-sdk-rust/)
70//! * [Usage examples](https://github.com/awslabs/aws-sdk-rust/tree/main/examples)
71//!
72//!
73//! # Crate Organization
74//!
75//! The entry point for most customers will be [`Client`], which exposes one method for each API
76//! offered by Amazon Aurora DSQL. The return value of each of these methods is a "fluent builder",
77//! where the different inputs for that API are added by builder-style function call chaining,
78//! followed by calling `send()` to get a [`Future`](std::future::Future) that will result in
79//! either a successful output or a [`SdkError`](crate::error::SdkError).
80//!
81//! Some of these API inputs may be structs or enums to provide more complex structured information.
82//! These structs and enums live in [`types`](crate::types). There are some simpler types for
83//! representing data such as date times or binary blobs that live in [`primitives`](crate::primitives).
84//!
85//! All types required to configure a client via the [`Config`](crate::Config) struct live
86//! in [`config`](crate::config).
87//!
88//! The [`operation`](crate::operation) module has a submodule for every API, and in each submodule
89//! is the input, output, and error type for that API, as well as builders to construct each of those.
90//!
91//! There is a top-level [`Error`](crate::Error) type that encompasses all the errors that the
92//! client can return. Any other error type can be converted to this `Error` type via the
93//! [`From`](std::convert::From) trait.
94//!
95//! The other modules within this crate are not required for normal usage.
96
97// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
98pub use error_meta::Error;
99
100#[doc(inline)]
101pub use config::Config;
102
103// include crate::auth_token;
104
105/// Client for calling Amazon Aurora DSQL.
106/// ## Constructing a `Client`
107///
108/// A [`Config`] is required to construct a client. For most use cases, the [`aws-config`]
109/// crate should be used to automatically resolve this config using
110/// [`aws_config::load_from_env()`], since this will resolve an [`SdkConfig`] which can be shared
111/// across multiple different AWS SDK clients. This config resolution process can be customized
112/// by calling [`aws_config::from_env()`] instead, which returns a [`ConfigLoader`] that uses
113/// the [builder pattern] to customize the default config.
114///
115/// In the simplest case, creating a client looks as follows:
116/// ```rust,no_run
117/// # async fn wrapper() {
118/// let config = aws_config::load_from_env().await;
119/// let client = aws_sdk_dsql::Client::new(&config);
120/// # }
121/// ```
122///
123/// Occasionally, SDKs may have additional service-specific values that can be set on the [`Config`] that
124/// is absent from [`SdkConfig`], or slightly different settings for a specific client may be desired.
125/// The [`Builder`](crate::config::Builder) struct implements `From<&SdkConfig>`, so setting these specific settings can be
126/// done as follows:
127///
128/// ```rust,no_run
129/// # async fn wrapper() {
130/// let sdk_config = ::aws_config::load_from_env().await;
131/// let config = aws_sdk_dsql::config::Builder::from(&sdk_config)
132/// # /*
133///     .some_service_specific_setting("value")
134/// # */
135///     .build();
136/// # }
137/// ```
138///
139/// See the [`aws-config` docs] and [`Config`] for more information on customizing configuration.
140///
141/// _Note:_ Client construction is expensive due to connection thread pool initialization, and should
142/// be done once at application start-up.
143///
144/// [`Config`]: crate::Config
145/// [`ConfigLoader`]: https://docs.rs/aws-config/*/aws_config/struct.ConfigLoader.html
146/// [`SdkConfig`]: https://docs.rs/aws-config/*/aws_config/struct.SdkConfig.html
147/// [`aws-config` docs]: https://docs.rs/aws-config/*
148/// [`aws-config`]: https://crates.io/crates/aws-config
149/// [`aws_config::from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.from_env.html
150/// [`aws_config::load_from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.load_from_env.html
151/// [builder pattern]: https://rust-lang.github.io/api-guidelines/type-safety.html#builders-enable-construction-of-complex-values-c-builder
152/// # Using the `Client`
153///
154/// A client has a function for every operation that can be performed by the service.
155/// For example, the [`CreateCluster`](crate::operation::create_cluster) operation has
156/// a [`Client::create_cluster`], function which returns a builder for that operation.
157/// The fluent builder ultimately has a `send()` function that returns an async future that
158/// returns a result, as illustrated below:
159///
160/// ```rust,ignore
161/// let result = client.create_cluster()
162///     .client_token("example")
163///     .send()
164///     .await;
165/// ```
166///
167/// The underlying HTTP requests that get made by this can be modified with the `customize_operation`
168/// function on the fluent builder. See the [`customize`](crate::client::customize) module for more
169/// information.
170/// # Waiters
171///
172/// This client provides `wait_until` methods behind the [`Waiters`](crate::client::Waiters) trait.
173/// To use them, simply import the trait, and then call one of the `wait_until` methods. This will
174/// return a waiter fluent builder that takes various parameters, which are documented on the builder
175/// type. Once parameters have been provided, the `wait` method can be called to initiate waiting.
176///
177/// For example, if there was a `wait_until_thing` method, it could look like:
178/// ```rust,ignore
179/// let result = client.wait_until_thing()
180///     .thing_id("someId")
181///     .wait(Duration::from_secs(120))
182///     .await;
183/// ```
184pub mod client;
185
186/// Configuration for Amazon Aurora DSQL.
187pub mod config;
188
189/// Common errors and error handling utilities.
190pub mod error;
191
192mod error_meta;
193
194/// Information about this crate.
195pub mod meta;
196
197/// All operations that this crate can perform.
198pub mod operation;
199
200/// Primitives such as `Blob` or `DateTime` used by other types.
201pub mod primitives;
202
203/// Data structures used by operation inputs/outputs.
204pub mod types;
205
206mod auth_plugin;
207
208pub mod auth_token;
209
210pub(crate) mod client_idempotency_token;
211
212mod idempotency_token;
213
214pub(crate) mod protocol_serde;
215
216mod sdk_feature_tracker;
217
218mod serialization_settings;
219
220mod endpoint_lib;
221
222mod lens;
223
224mod serde_util;
225
226/// Supporting types for waiters.
227///
228/// Note: to use waiters, import the [`Waiters`](crate::client::Waiters) trait, which adds methods prefixed with `wait_until` to the client.
229pub mod waiters;
230
231mod json_errors;
232
233#[doc(inline)]
234pub use client::Client;