aws_sdk_appstream/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 AppStream
10///
11/// Client for invoking operations on Amazon AppStream. Each operation on Amazon AppStream 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_appstream::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_appstream::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 [`AssociateAppBlockBuilderAppBlock`](crate::operation::associate_app_block_builder_app_block) operation has
63/// a [`Client::associate_app_block_builder_app_block`], 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.associate_app_block_builder_app_block()
69/// .app_block_arn("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 for `fleet_started`
144 fn wait_until_fleet_started(&self) -> crate::waiters::fleet_started::FleetStartedFluentBuilder;
145 /// Wait for `fleet_stopped`
146 fn wait_until_fleet_stopped(&self) -> crate::waiters::fleet_stopped::FleetStoppedFluentBuilder;
147}
148impl Waiters for Client {
149 fn wait_until_fleet_started(&self) -> crate::waiters::fleet_started::FleetStartedFluentBuilder {
150 crate::waiters::fleet_started::FleetStartedFluentBuilder::new(self.handle.clone())
151 }
152 fn wait_until_fleet_stopped(&self) -> crate::waiters::fleet_stopped::FleetStoppedFluentBuilder {
153 crate::waiters::fleet_stopped::FleetStoppedFluentBuilder::new(self.handle.clone())
154 }
155}
156
157impl Client {
158 /// Creates a new client from an [SDK Config](::aws_types::sdk_config::SdkConfig).
159 ///
160 /// # Panics
161 ///
162 /// - This method will panic if the `sdk_config` is missing an async sleep implementation. If you experience this panic, set
163 /// the `sleep_impl` on the Config passed into this function to fix it.
164 /// - This method will panic if the `sdk_config` is missing an HTTP connector. If you experience this panic, set the
165 /// `http_connector` on the Config passed into this function to fix it.
166 /// - 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.
167 #[track_caller]
168 pub fn new(sdk_config: &::aws_types::sdk_config::SdkConfig) -> Self {
169 Self::from_conf(sdk_config.into())
170 }
171}
172
173mod associate_app_block_builder_app_block;
174
175mod associate_application_fleet;
176
177mod associate_application_to_entitlement;
178
179mod associate_fleet;
180
181mod associate_software_to_image_builder;
182
183mod batch_associate_user_stack;
184
185mod batch_disassociate_user_stack;
186
187mod copy_image;
188
189mod create_app_block;
190
191mod create_app_block_builder;
192
193mod create_app_block_builder_streaming_url;
194
195mod create_application;
196
197mod create_directory_config;
198
199mod create_entitlement;
200
201mod create_export_image_task;
202
203mod create_fleet;
204
205mod create_image_builder;
206
207mod create_image_builder_streaming_url;
208
209mod create_imported_image;
210
211mod create_stack;
212
213mod create_streaming_url;
214
215mod create_theme_for_stack;
216
217mod create_updated_image;
218
219mod create_usage_report_subscription;
220
221mod create_user;
222
223/// Operation customization and supporting types.
224///
225/// The underlying HTTP requests made during an operation can be customized
226/// by calling the `customize()` method on the builder returned from a client
227/// operation call. For example, this can be used to add an additional HTTP header:
228///
229/// ```ignore
230/// # async fn wrapper() -> ::std::result::Result<(), aws_sdk_appstream::Error> {
231/// # let client: aws_sdk_appstream::Client = unimplemented!();
232/// use ::http::header::{HeaderName, HeaderValue};
233///
234/// let result = client.associate_app_block_builder_app_block()
235/// .customize()
236/// .mutate_request(|req| {
237/// // Add `x-example-header` with value
238/// req.headers_mut()
239/// .insert(
240/// HeaderName::from_static("x-example-header"),
241/// HeaderValue::from_static("1"),
242/// );
243/// })
244/// .send()
245/// .await;
246/// # }
247/// ```
248pub mod customize;
249
250mod delete_app_block;
251
252mod delete_app_block_builder;
253
254mod delete_application;
255
256mod delete_directory_config;
257
258mod delete_entitlement;
259
260mod delete_fleet;
261
262mod delete_image;
263
264mod delete_image_builder;
265
266mod delete_image_permissions;
267
268mod delete_stack;
269
270mod delete_theme_for_stack;
271
272mod delete_usage_report_subscription;
273
274mod delete_user;
275
276mod describe_app_block_builder_app_block_associations;
277
278mod describe_app_block_builders;
279
280mod describe_app_blocks;
281
282mod describe_app_license_usage;
283
284mod describe_application_fleet_associations;
285
286mod describe_applications;
287
288mod describe_directory_configs;
289
290mod describe_entitlements;
291
292mod describe_fleets;
293
294mod describe_image_builders;
295
296mod describe_image_permissions;
297
298mod describe_images;
299
300mod describe_sessions;
301
302mod describe_software_associations;
303
304mod describe_stacks;
305
306mod describe_theme_for_stack;
307
308mod describe_usage_report_subscriptions;
309
310mod describe_user_stack_associations;
311
312mod describe_users;
313
314mod disable_user;
315
316mod disassociate_app_block_builder_app_block;
317
318mod disassociate_application_fleet;
319
320mod disassociate_application_from_entitlement;
321
322mod disassociate_fleet;
323
324mod disassociate_software_from_image_builder;
325
326mod enable_user;
327
328mod expire_session;
329
330mod get_export_image_task;
331
332mod list_associated_fleets;
333
334mod list_associated_stacks;
335
336mod list_entitled_applications;
337
338mod list_export_image_tasks;
339
340mod list_tags_for_resource;
341
342mod start_app_block_builder;
343
344mod start_fleet;
345
346mod start_image_builder;
347
348mod start_software_deployment_to_image_builder;
349
350mod stop_app_block_builder;
351
352mod stop_fleet;
353
354mod stop_image_builder;
355
356mod tag_resource;
357
358mod untag_resource;
359
360mod update_app_block_builder;
361
362mod update_application;
363
364mod update_directory_config;
365
366mod update_entitlement;
367
368mod update_fleet;
369
370mod update_image_permissions;
371
372mod update_stack;
373
374mod update_theme_for_stack;