aws_sdk_neptunegraph/
client.rs

1// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
2#[derive(Debug)]
3pub(crate) struct Handle {
4    pub(crate) conf: crate::Config,
5    #[allow(dead_code)] // unused when a service does not provide any operations
6    pub(crate) runtime_plugins: ::aws_smithy_runtime_api::client::runtime_plugin::RuntimePlugins,
7}
8
9/// Client for Amazon Neptune Graph
10///
11/// Client for invoking operations on Amazon Neptune Graph. Each operation on Amazon Neptune Graph is a method on this
12/// this struct. `.send()` MUST be invoked on the generated operations to dispatch the request to the service.
13/// ## Constructing a `Client`
14///
15/// A [`Config`] is required to construct a client. For most use cases, the [`aws-config`]
16/// crate should be used to automatically resolve this config using
17/// [`aws_config::load_from_env()`], since this will resolve an [`SdkConfig`] which can be shared
18/// across multiple different AWS SDK clients. This config resolution process can be customized
19/// by calling [`aws_config::from_env()`] instead, which returns a [`ConfigLoader`] that uses
20/// the [builder pattern] to customize the default config.
21///
22/// In the simplest case, creating a client looks as follows:
23/// ```rust,no_run
24/// # async fn wrapper() {
25/// let config = aws_config::load_from_env().await;
26/// let client = aws_sdk_neptunegraph::Client::new(&config);
27/// # }
28/// ```
29///
30/// Occasionally, SDKs may have additional service-specific values that can be set on the [`Config`] that
31/// is absent from [`SdkConfig`], or slightly different settings for a specific client may be desired.
32/// The [`Builder`](crate::config::Builder) struct implements `From<&SdkConfig>`, so setting these specific settings can be
33/// done as follows:
34///
35/// ```rust,no_run
36/// # async fn wrapper() {
37/// let sdk_config = ::aws_config::load_from_env().await;
38/// let config = aws_sdk_neptunegraph::config::Builder::from(&sdk_config)
39/// # /*
40///     .some_service_specific_setting("value")
41/// # */
42///     .build();
43/// # }
44/// ```
45///
46/// See the [`aws-config` docs] and [`Config`] for more information on customizing configuration.
47///
48/// _Note:_ Client construction is expensive due to connection thread pool initialization, and should
49/// be done once at application start-up.
50///
51/// [`Config`]: crate::Config
52/// [`ConfigLoader`]: https://docs.rs/aws-config/*/aws_config/struct.ConfigLoader.html
53/// [`SdkConfig`]: https://docs.rs/aws-config/*/aws_config/struct.SdkConfig.html
54/// [`aws-config` docs]: https://docs.rs/aws-config/*
55/// [`aws-config`]: https://crates.io/crates/aws-config
56/// [`aws_config::from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.from_env.html
57/// [`aws_config::load_from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.load_from_env.html
58/// [builder pattern]: https://rust-lang.github.io/api-guidelines/type-safety.html#builders-enable-construction-of-complex-values-c-builder
59/// # Using the `Client`
60///
61/// A client has a function for every operation that can be performed by the service.
62/// For example, the [`CancelExportTask`](crate::operation::cancel_export_task) operation has
63/// a [`Client::cancel_export_task`], function which returns a builder for that operation.
64/// The fluent builder ultimately has a `send()` function that returns an async future that
65/// returns a result, as illustrated below:
66///
67/// ```rust,ignore
68/// let result = client.cancel_export_task()
69///     .task_identifier("example")
70///     .send()
71///     .await;
72/// ```
73///
74/// The underlying HTTP requests that get made by this can be modified with the `customize_operation`
75/// function on the fluent builder. See the [`customize`](crate::client::customize) module for more
76/// information.
77/// # Waiters
78///
79/// This client provides `wait_until` methods behind the [`Waiters`](crate::client::Waiters) trait.
80/// To use them, simply import the trait, and then call one of the `wait_until` methods. This will
81/// return a waiter fluent builder that takes various parameters, which are documented on the builder
82/// type. Once parameters have been provided, the `wait` method can be called to initiate waiting.
83///
84/// For example, if there was a `wait_until_thing` method, it could look like:
85/// ```rust,ignore
86/// let result = client.wait_until_thing()
87///     .thing_id("someId")
88///     .wait(Duration::from_secs(120))
89///     .await;
90/// ```
91#[derive(::std::clone::Clone, ::std::fmt::Debug)]
92pub struct Client {
93    handle: ::std::sync::Arc<Handle>,
94}
95
96impl Client {
97    /// Creates a new client from the service [`Config`](crate::Config).
98    ///
99    /// # Panics
100    ///
101    /// This method will panic in the following cases:
102    ///
103    /// - Retries or timeouts are enabled without a `sleep_impl` configured.
104    /// - Identity caching is enabled without a `sleep_impl` and `time_source` configured.
105    /// - No `behavior_version` is provided.
106    ///
107    /// The panic message for each of these will have instructions on how to resolve them.
108    #[track_caller]
109    pub fn from_conf(conf: crate::Config) -> Self {
110        let handle = Handle {
111            conf: conf.clone(),
112            runtime_plugins: crate::config::base_client_runtime_plugins(conf),
113        };
114        if let Err(err) = Self::validate_config(&handle) {
115            panic!("Invalid client configuration: {err}");
116        }
117        Self {
118            handle: ::std::sync::Arc::new(handle),
119        }
120    }
121
122    /// Returns the client's configuration.
123    pub fn config(&self) -> &crate::Config {
124        &self.handle.conf
125    }
126
127    fn validate_config(handle: &Handle) -> ::std::result::Result<(), ::aws_smithy_runtime_api::box_error::BoxError> {
128        let mut cfg = ::aws_smithy_types::config_bag::ConfigBag::base();
129        handle
130            .runtime_plugins
131            .apply_client_configuration(&mut cfg)?
132            .validate_base_client_config(&cfg)?;
133        Ok(())
134    }
135}
136
137///
138/// Waiter functions for the client.
139///
140/// Import this trait to get `wait_until` methods on the client.
141///
142pub trait Waiters {
143    /// Wait until Export Task is Successful
144    fn wait_until_export_task_successful(&self) -> crate::waiters::export_task_successful::ExportTaskSuccessfulFluentBuilder;
145    /// Wait until Export Task is Cancelled
146    fn wait_until_export_task_cancelled(&self) -> crate::waiters::export_task_cancelled::ExportTaskCancelledFluentBuilder;
147    /// Wait until Graph is Available
148    fn wait_until_graph_available(&self) -> crate::waiters::graph_available::GraphAvailableFluentBuilder;
149    /// Wait until Graph is Deleted
150    fn wait_until_graph_deleted(&self) -> crate::waiters::graph_deleted::GraphDeletedFluentBuilder;
151    /// Wait until Graph is Stopped
152    fn wait_until_graph_stopped(&self) -> crate::waiters::graph_stopped::GraphStoppedFluentBuilder;
153    /// Wait until GraphSnapshot is Available
154    fn wait_until_graph_snapshot_available(&self) -> crate::waiters::graph_snapshot_available::GraphSnapshotAvailableFluentBuilder;
155    /// Wait until GraphSnapshot is Deleted
156    fn wait_until_graph_snapshot_deleted(&self) -> crate::waiters::graph_snapshot_deleted::GraphSnapshotDeletedFluentBuilder;
157    /// Wait until Import Task is Successful
158    fn wait_until_import_task_successful(&self) -> crate::waiters::import_task_successful::ImportTaskSuccessfulFluentBuilder;
159    /// Wait until Import Task is Cancelled
160    fn wait_until_import_task_cancelled(&self) -> crate::waiters::import_task_cancelled::ImportTaskCancelledFluentBuilder;
161    /// Wait until PrivateGraphEndpoint is Available
162    fn wait_until_private_graph_endpoint_available(
163        &self,
164    ) -> crate::waiters::private_graph_endpoint_available::PrivateGraphEndpointAvailableFluentBuilder;
165    /// Wait until PrivateGraphEndpoint is Deleted
166    fn wait_until_private_graph_endpoint_deleted(&self) -> crate::waiters::private_graph_endpoint_deleted::PrivateGraphEndpointDeletedFluentBuilder;
167}
168impl Waiters for Client {
169    fn wait_until_export_task_successful(&self) -> crate::waiters::export_task_successful::ExportTaskSuccessfulFluentBuilder {
170        crate::waiters::export_task_successful::ExportTaskSuccessfulFluentBuilder::new(self.handle.clone())
171    }
172    fn wait_until_export_task_cancelled(&self) -> crate::waiters::export_task_cancelled::ExportTaskCancelledFluentBuilder {
173        crate::waiters::export_task_cancelled::ExportTaskCancelledFluentBuilder::new(self.handle.clone())
174    }
175    fn wait_until_graph_available(&self) -> crate::waiters::graph_available::GraphAvailableFluentBuilder {
176        crate::waiters::graph_available::GraphAvailableFluentBuilder::new(self.handle.clone())
177    }
178    fn wait_until_graph_deleted(&self) -> crate::waiters::graph_deleted::GraphDeletedFluentBuilder {
179        crate::waiters::graph_deleted::GraphDeletedFluentBuilder::new(self.handle.clone())
180    }
181    fn wait_until_graph_stopped(&self) -> crate::waiters::graph_stopped::GraphStoppedFluentBuilder {
182        crate::waiters::graph_stopped::GraphStoppedFluentBuilder::new(self.handle.clone())
183    }
184    fn wait_until_graph_snapshot_available(&self) -> crate::waiters::graph_snapshot_available::GraphSnapshotAvailableFluentBuilder {
185        crate::waiters::graph_snapshot_available::GraphSnapshotAvailableFluentBuilder::new(self.handle.clone())
186    }
187    fn wait_until_graph_snapshot_deleted(&self) -> crate::waiters::graph_snapshot_deleted::GraphSnapshotDeletedFluentBuilder {
188        crate::waiters::graph_snapshot_deleted::GraphSnapshotDeletedFluentBuilder::new(self.handle.clone())
189    }
190    fn wait_until_import_task_successful(&self) -> crate::waiters::import_task_successful::ImportTaskSuccessfulFluentBuilder {
191        crate::waiters::import_task_successful::ImportTaskSuccessfulFluentBuilder::new(self.handle.clone())
192    }
193    fn wait_until_import_task_cancelled(&self) -> crate::waiters::import_task_cancelled::ImportTaskCancelledFluentBuilder {
194        crate::waiters::import_task_cancelled::ImportTaskCancelledFluentBuilder::new(self.handle.clone())
195    }
196    fn wait_until_private_graph_endpoint_available(
197        &self,
198    ) -> crate::waiters::private_graph_endpoint_available::PrivateGraphEndpointAvailableFluentBuilder {
199        crate::waiters::private_graph_endpoint_available::PrivateGraphEndpointAvailableFluentBuilder::new(self.handle.clone())
200    }
201    fn wait_until_private_graph_endpoint_deleted(&self) -> crate::waiters::private_graph_endpoint_deleted::PrivateGraphEndpointDeletedFluentBuilder {
202        crate::waiters::private_graph_endpoint_deleted::PrivateGraphEndpointDeletedFluentBuilder::new(self.handle.clone())
203    }
204}
205
206impl Client {
207    /// Creates a new client from an [SDK Config](::aws_types::sdk_config::SdkConfig).
208    ///
209    /// # Panics
210    ///
211    /// - This method will panic if the `sdk_config` is missing an async sleep implementation. If you experience this panic, set
212    ///   the `sleep_impl` on the Config passed into this function to fix it.
213    /// - This method will panic if the `sdk_config` is missing an HTTP connector. If you experience this panic, set the
214    ///   `http_connector` on the Config passed into this function to fix it.
215    /// - This method will panic if no `BehaviorVersion` is provided. If you experience this panic, set `behavior_version` on the Config or enable the `behavior-version-latest` Cargo feature.
216    #[track_caller]
217    pub fn new(sdk_config: &::aws_types::sdk_config::SdkConfig) -> Self {
218        Self::from_conf(sdk_config.into())
219    }
220}
221
222mod cancel_export_task;
223
224mod cancel_import_task;
225
226mod cancel_query;
227
228mod create_graph;
229
230mod create_graph_snapshot;
231
232mod create_graph_using_import_task;
233
234mod create_private_graph_endpoint;
235
236/// Operation customization and supporting types.
237///
238/// The underlying HTTP requests made during an operation can be customized
239/// by calling the `customize()` method on the builder returned from a client
240/// operation call. For example, this can be used to add an additional HTTP header:
241///
242/// ```ignore
243/// # async fn wrapper() -> ::std::result::Result<(), aws_sdk_neptunegraph::Error> {
244/// # let client: aws_sdk_neptunegraph::Client = unimplemented!();
245/// use ::http::header::{HeaderName, HeaderValue};
246///
247/// let result = client.cancel_export_task()
248///     .customize()
249///     .mutate_request(|req| {
250///         // Add `x-example-header` with value
251///         req.headers_mut()
252///             .insert(
253///                 HeaderName::from_static("x-example-header"),
254///                 HeaderValue::from_static("1"),
255///             );
256///     })
257///     .send()
258///     .await;
259/// # }
260/// ```
261pub mod customize;
262
263mod delete_graph;
264
265mod delete_graph_snapshot;
266
267mod delete_private_graph_endpoint;
268
269mod execute_query;
270
271mod get_export_task;
272
273mod get_graph;
274
275mod get_graph_snapshot;
276
277mod get_graph_summary;
278
279mod get_import_task;
280
281mod get_private_graph_endpoint;
282
283mod get_query;
284
285mod list_export_tasks;
286
287mod list_graph_snapshots;
288
289mod list_graphs;
290
291mod list_import_tasks;
292
293mod list_private_graph_endpoints;
294
295mod list_queries;
296
297mod list_tags_for_resource;
298
299mod reset_graph;
300
301mod restore_graph_from_snapshot;
302
303mod start_export_task;
304
305mod start_graph;
306
307mod start_import_task;
308
309mod stop_graph;
310
311mod tag_resource;
312
313mod untag_resource;
314
315mod update_graph;