1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265
/*
* Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
* SPDX-License-Identifier: Apache-2.0
*/
//! A Hyper-based Smithy service client.
//!
//! | Feature | Description |
//! |-------------------|-------------|
//! | `event-stream` | Provides Sender/Receiver implementations for Event Stream codegen. |
//! | `rt-tokio` | Run async code with the `tokio` runtime |
//! | `test-util` | Include various testing utils |
//! | `native-tls` | Use `native-tls` as the HTTP client's TLS implementation |
//! | `rustls` | Use `rustls` as the HTTP client's TLS implementation |
//! | `client-hyper` | Use `hyper` to handle HTTP requests |
#![allow(clippy::derive_partial_eq_without_eq)]
#![warn(
missing_docs,
rustdoc::missing_crate_level_docs,
unreachable_pub,
rust_2018_idioms
)]
pub mod bounds;
pub mod erase;
pub mod http_connector;
pub mod never;
mod poison;
pub mod retry;
pub mod timeout;
// https://github.com/rust-lang/rust/issues/72081
#[allow(rustdoc::private_doc_tests)]
mod builder;
pub use builder::Builder;
#[cfg(feature = "test-util")]
pub mod dvr;
#[cfg(feature = "test-util")]
pub mod test_connection;
#[cfg(feature = "client-hyper")]
pub mod conns;
#[cfg(feature = "client-hyper")]
pub mod hyper_ext;
// The types in this module are only used to write the bounds in [`Client::check`]. Customers will
// not need them. But the module and its types must be public so that we can call `check` from
// doc-tests.
#[doc(hidden)]
pub mod static_tests;
use crate::poison::PoisonLayer;
use aws_smithy_async::rt::sleep::AsyncSleep;
use aws_smithy_http::operation::Operation;
use aws_smithy_http::response::ParseHttpResponse;
pub use aws_smithy_http::result::{SdkError, SdkSuccess};
use aws_smithy_http::retry::ClassifyRetry;
use aws_smithy_http_tower::dispatch::DispatchLayer;
use aws_smithy_http_tower::parse_response::ParseResponseLayer;
use aws_smithy_types::error::display::DisplayErrorContext;
use aws_smithy_types::retry::{ProvideErrorKind, ReconnectMode};
use aws_smithy_types::timeout::OperationTimeoutConfig;
use std::sync::Arc;
use timeout::ClientTimeoutParams;
pub use timeout::TimeoutLayer;
use tower::{Service, ServiceBuilder, ServiceExt};
use tracing::{debug_span, field, Instrument};
/// Smithy service client.
///
/// The service client is customizable in a number of ways (see [`Builder`]), but most customers
/// can stick with the standard constructor provided by [`Client::new`]. It takes only a single
/// argument, which is the middleware that fills out the [`http::Request`] for each higher-level
/// operation so that it can ultimately be sent to the remote host. The middleware is responsible
/// for filling in any request parameters that aren't specified by the Smithy protocol definition,
/// such as those used for routing (like the URL), authentication, and authorization.
///
/// The middleware takes the form of a [`tower::Layer`] that wraps the actual connection for each
/// request. The [`tower::Service`](Service) that the middleware produces must accept requests of the type
/// [`aws_smithy_http::operation::Request`] and return responses of the type
/// [`http::Response<SdkBody>`], most likely by modifying the provided request in place, passing it
/// to the inner service, and then ultimately returning the inner service's response.
///
/// With the `hyper` feature enabled, you can construct a `Client` directly from a
/// `hyper::Client` using `hyper_ext::Adapter::builder`. You can also enable the `rustls` or `native-tls`
/// features to construct a Client against a standard HTTPS endpoint using `Builder::rustls_connector` and
/// `Builder::native_tls_connector` respectively.
#[derive(Debug)]
pub struct Client<
Connector = erase::DynConnector,
Middleware = erase::DynMiddleware<Connector>,
RetryPolicy = retry::Standard,
> {
connector: Connector,
middleware: Middleware,
retry_policy: RetryPolicy,
reconnect_mode: ReconnectMode,
operation_timeout_config: OperationTimeoutConfig,
sleep_impl: Option<Arc<dyn AsyncSleep>>,
}
impl Client<(), (), ()> {
/// Returns a client builder
pub fn builder() -> Builder {
Builder::new()
}
}
// Quick-create for people who just want "the default".
impl<C, M> Client<C, M>
where
M: Default,
{
/// Create a Smithy client from the given `connector`, a middleware default, the
/// [standard retry policy](retry::Standard), and the
/// [`default_async_sleep`](aws_smithy_async::rt::sleep::default_async_sleep) sleep implementation.
pub fn new(connector: C) -> Self {
Builder::new()
.connector(connector)
.middleware(M::default())
.build()
}
}
fn check_send_sync<T: Send + Sync>(t: T) -> T {
t
}
impl<C, M, R> Client<C, M, R>
where
C: bounds::SmithyConnector,
M: bounds::SmithyMiddleware<C>,
R: retry::NewRequestPolicy,
{
/// Dispatch this request to the network
///
/// For ergonomics, this does not include the raw response for successful responses. To
/// access the raw response use `call_raw`.
pub async fn call<O, T, E, Retry>(&self, op: Operation<O, Retry>) -> Result<T, SdkError<E>>
where
O: Send + Sync,
E: std::error::Error + Send + Sync + 'static,
Retry: Send + Sync,
R::Policy: bounds::SmithyRetryPolicy<O, T, E, Retry>,
Retry: ClassifyRetry<SdkSuccess<T>, SdkError<E>>,
bounds::Parsed<<M as bounds::SmithyMiddleware<C>>::Service, O, Retry>:
Service<Operation<O, Retry>, Response = SdkSuccess<T>, Error = SdkError<E>> + Clone,
{
self.call_raw(op).await.map(|res| res.parsed)
}
/// Dispatch this request to the network
///
/// The returned result contains the raw HTTP response which can be useful for debugging or
/// implementing unsupported features.
pub async fn call_raw<O, T, E, Retry>(
&self,
op: Operation<O, Retry>,
) -> Result<SdkSuccess<T>, SdkError<E>>
where
O: Send + Sync,
E: std::error::Error + Send + Sync + 'static,
Retry: Send + Sync,
R::Policy: bounds::SmithyRetryPolicy<O, T, E, Retry>,
Retry: ClassifyRetry<SdkSuccess<T>, SdkError<E>>,
// This bound is not _technically_ inferred by all the previous bounds, but in practice it
// is because _we_ know that there is only implementation of Service for Parsed
// (ParsedResponseService), and it will apply as long as the bounds on C, M, and R hold,
// and will produce (as expected) Response = SdkSuccess<T>, Error = SdkError<E>. But Rust
// doesn't know that -- there _could_ theoretically be other implementations of Service for
// Parsed that don't return those same types. So, we must give the bound.
bounds::Parsed<<M as bounds::SmithyMiddleware<C>>::Service, O, Retry>:
Service<Operation<O, Retry>, Response = SdkSuccess<T>, Error = SdkError<E>> + Clone,
{
let connector = self.connector.clone();
let timeout_params =
ClientTimeoutParams::new(&self.operation_timeout_config, self.sleep_impl.clone());
let svc = ServiceBuilder::new()
.layer(TimeoutLayer::new(timeout_params.operation_timeout))
.retry(
self.retry_policy
.new_request_policy(self.sleep_impl.clone()),
)
.layer(PoisonLayer::new(self.reconnect_mode))
.layer(TimeoutLayer::new(timeout_params.operation_attempt_timeout))
.layer(ParseResponseLayer::<O, Retry>::new())
// These layers can be considered as occurring in order. That is, first invoke the
// customer-provided middleware, then dispatch dispatch over the wire.
.layer(&self.middleware)
.layer(DispatchLayer::new())
.service(connector);
// send_operation records the full request-response lifecycle.
// NOTE: For operations that stream output, only the setup is captured in this span.
let span = debug_span!(
"send_operation",
operation = field::Empty,
service = field::Empty,
status = field::Empty,
message = field::Empty
);
let (mut req, parts) = op.into_request_response();
if let Some(metadata) = &parts.metadata {
// Clippy has a bug related to needless borrows so we need to allow them here
// https://github.com/rust-lang/rust-clippy/issues/9782
#[allow(clippy::needless_borrow)]
{
span.record("operation", &metadata.name());
span.record("service", &metadata.service());
}
// This will clone two `Cow::<&'static str>::Borrow`s in the vast majority of cases
req.properties_mut().insert(metadata.clone());
}
let op = Operation::from_parts(req, parts);
let result = async move { check_send_sync(svc).ready().await?.call(op).await }
.instrument(span.clone())
.await;
#[allow(clippy::needless_borrow)]
match &result {
Ok(_) => {
span.record("status", &"ok");
}
Err(err) => {
span.record(
"status",
&match err {
SdkError::ConstructionFailure(_) => "construction_failure",
SdkError::DispatchFailure(_) => "dispatch_failure",
SdkError::ResponseError(_) => "response_error",
SdkError::ServiceError(_) => "service_error",
SdkError::TimeoutError(_) => "timeout_error",
_ => "error",
},
)
.record("message", &field::display(DisplayErrorContext(err)));
}
}
result
}
/// Statically check the validity of a `Client` without a request to send.
///
/// This will make sure that all the bounds hold that would be required by `call` and
/// `call_raw` (modulo those that relate to the specific `Operation` type). Comes in handy to
/// ensure (statically) that all the various constructors actually produce "useful" types.
#[doc(hidden)]
pub fn check(&self)
where
R::Policy: tower::retry::Policy<
static_tests::ValidTestOperation,
SdkSuccess<()>,
SdkError<static_tests::TestOperationError>,
> + Clone,
{
let _ = |o: static_tests::ValidTestOperation| {
drop(self.call_raw(o));
};
}
}