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