aws_sdk_cloudformation/
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 AWS CloudFormation
10///
11/// Client for invoking operations on AWS CloudFormation. Each operation on AWS CloudFormation 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_cloudformation::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_cloudformation::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 [`ActivateType`](crate::operation::activate_type) operation has
63/// a [`Client::activate_type`], 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.activate_type()
69///     .r#type("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 change set status is CREATE_COMPLETE.
144    fn wait_until_change_set_create_complete(&self) -> crate::waiters::change_set_create_complete::ChangeSetCreateCompleteFluentBuilder;
145    /// Wait until the stack refactor status is CREATE_COMPLETE.
146    fn wait_until_stack_refactor_create_complete(&self) -> crate::waiters::stack_refactor_create_complete::StackRefactorCreateCompleteFluentBuilder;
147    /// Wait until the stack refactor status is EXECUTE_COMPLETE.
148    fn wait_until_stack_refactor_execute_complete(
149        &self,
150    ) -> crate::waiters::stack_refactor_execute_complete::StackRefactorExecuteCompleteFluentBuilder;
151    /// Wait until stack status is CREATE_COMPLETE.
152    fn wait_until_stack_create_complete(&self) -> crate::waiters::stack_create_complete::StackCreateCompleteFluentBuilder;
153    /// Wait until stack status is DELETE_COMPLETE.
154    fn wait_until_stack_delete_complete(&self) -> crate::waiters::stack_delete_complete::StackDeleteCompleteFluentBuilder;
155    /// Wait for `stack_exists`
156    fn wait_until_stack_exists(&self) -> crate::waiters::stack_exists::StackExistsFluentBuilder;
157    /// Wait until stack status is IMPORT_COMPLETE.
158    fn wait_until_stack_import_complete(&self) -> crate::waiters::stack_import_complete::StackImportCompleteFluentBuilder;
159    /// Wait until stack status is UPDATE_ROLLBACK_COMPLETE.
160    fn wait_until_stack_rollback_complete(&self) -> crate::waiters::stack_rollback_complete::StackRollbackCompleteFluentBuilder;
161    /// Wait until stack status is UPDATE_COMPLETE.
162    fn wait_until_stack_update_complete(&self) -> crate::waiters::stack_update_complete::StackUpdateCompleteFluentBuilder;
163    /// Wait until type registration is COMPLETE.
164    fn wait_until_type_registration_complete(&self) -> crate::waiters::type_registration_complete::TypeRegistrationCompleteFluentBuilder;
165}
166impl Waiters for Client {
167    fn wait_until_change_set_create_complete(&self) -> crate::waiters::change_set_create_complete::ChangeSetCreateCompleteFluentBuilder {
168        crate::waiters::change_set_create_complete::ChangeSetCreateCompleteFluentBuilder::new(self.handle.clone())
169    }
170    fn wait_until_stack_refactor_create_complete(&self) -> crate::waiters::stack_refactor_create_complete::StackRefactorCreateCompleteFluentBuilder {
171        crate::waiters::stack_refactor_create_complete::StackRefactorCreateCompleteFluentBuilder::new(self.handle.clone())
172    }
173    fn wait_until_stack_refactor_execute_complete(
174        &self,
175    ) -> crate::waiters::stack_refactor_execute_complete::StackRefactorExecuteCompleteFluentBuilder {
176        crate::waiters::stack_refactor_execute_complete::StackRefactorExecuteCompleteFluentBuilder::new(self.handle.clone())
177    }
178    fn wait_until_stack_create_complete(&self) -> crate::waiters::stack_create_complete::StackCreateCompleteFluentBuilder {
179        crate::waiters::stack_create_complete::StackCreateCompleteFluentBuilder::new(self.handle.clone())
180    }
181    fn wait_until_stack_delete_complete(&self) -> crate::waiters::stack_delete_complete::StackDeleteCompleteFluentBuilder {
182        crate::waiters::stack_delete_complete::StackDeleteCompleteFluentBuilder::new(self.handle.clone())
183    }
184    fn wait_until_stack_exists(&self) -> crate::waiters::stack_exists::StackExistsFluentBuilder {
185        crate::waiters::stack_exists::StackExistsFluentBuilder::new(self.handle.clone())
186    }
187    fn wait_until_stack_import_complete(&self) -> crate::waiters::stack_import_complete::StackImportCompleteFluentBuilder {
188        crate::waiters::stack_import_complete::StackImportCompleteFluentBuilder::new(self.handle.clone())
189    }
190    fn wait_until_stack_rollback_complete(&self) -> crate::waiters::stack_rollback_complete::StackRollbackCompleteFluentBuilder {
191        crate::waiters::stack_rollback_complete::StackRollbackCompleteFluentBuilder::new(self.handle.clone())
192    }
193    fn wait_until_stack_update_complete(&self) -> crate::waiters::stack_update_complete::StackUpdateCompleteFluentBuilder {
194        crate::waiters::stack_update_complete::StackUpdateCompleteFluentBuilder::new(self.handle.clone())
195    }
196    fn wait_until_type_registration_complete(&self) -> crate::waiters::type_registration_complete::TypeRegistrationCompleteFluentBuilder {
197        crate::waiters::type_registration_complete::TypeRegistrationCompleteFluentBuilder::new(self.handle.clone())
198    }
199}
200
201impl Client {
202    /// Creates a new client from an [SDK Config](::aws_types::sdk_config::SdkConfig).
203    ///
204    /// # Panics
205    ///
206    /// - This method will panic if the `sdk_config` is missing an async sleep implementation. If you experience this panic, set
207    ///     the `sleep_impl` on the Config passed into this function to fix it.
208    /// - This method will panic if the `sdk_config` is missing an HTTP connector. If you experience this panic, set the
209    ///     `http_connector` on the Config passed into this function to fix it.
210    /// - 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.
211    #[track_caller]
212    pub fn new(sdk_config: &::aws_types::sdk_config::SdkConfig) -> Self {
213        Self::from_conf(sdk_config.into())
214    }
215}
216
217mod activate_organizations_access;
218
219mod activate_type;
220
221mod batch_describe_type_configurations;
222
223mod cancel_update_stack;
224
225mod continue_update_rollback;
226
227mod create_change_set;
228
229mod create_generated_template;
230
231mod create_stack;
232
233mod create_stack_instances;
234
235mod create_stack_refactor;
236
237mod create_stack_set;
238
239/// Operation customization and supporting types.
240///
241/// The underlying HTTP requests made during an operation can be customized
242/// by calling the `customize()` method on the builder returned from a client
243/// operation call. For example, this can be used to add an additional HTTP header:
244///
245/// ```ignore
246/// # async fn wrapper() -> ::std::result::Result<(), aws_sdk_cloudformation::Error> {
247/// # let client: aws_sdk_cloudformation::Client = unimplemented!();
248/// use ::http::header::{HeaderName, HeaderValue};
249///
250/// let result = client.activate_organizations_access()
251///     .customize()
252///     .mutate_request(|req| {
253///         // Add `x-example-header` with value
254///         req.headers_mut()
255///             .insert(
256///                 HeaderName::from_static("x-example-header"),
257///                 HeaderValue::from_static("1"),
258///             );
259///     })
260///     .send()
261///     .await;
262/// # }
263/// ```
264pub mod customize;
265
266mod deactivate_organizations_access;
267
268mod deactivate_type;
269
270mod delete_change_set;
271
272mod delete_generated_template;
273
274mod delete_stack;
275
276mod delete_stack_instances;
277
278mod delete_stack_set;
279
280mod deregister_type;
281
282mod describe_account_limits;
283
284mod describe_change_set;
285
286mod describe_change_set_hooks;
287
288mod describe_generated_template;
289
290mod describe_organizations_access;
291
292mod describe_publisher;
293
294mod describe_resource_scan;
295
296mod describe_stack_drift_detection_status;
297
298mod describe_stack_events;
299
300mod describe_stack_instance;
301
302mod describe_stack_refactor;
303
304mod describe_stack_resource;
305
306mod describe_stack_resource_drifts;
307
308mod describe_stack_resources;
309
310mod describe_stack_set;
311
312mod describe_stack_set_operation;
313
314mod describe_stacks;
315
316mod describe_type;
317
318mod describe_type_registration;
319
320mod detect_stack_drift;
321
322mod detect_stack_resource_drift;
323
324mod detect_stack_set_drift;
325
326mod estimate_template_cost;
327
328mod execute_change_set;
329
330mod execute_stack_refactor;
331
332mod get_generated_template;
333
334mod get_stack_policy;
335
336mod get_template;
337
338mod get_template_summary;
339
340mod import_stacks_to_stack_set;
341
342mod list_change_sets;
343
344mod list_exports;
345
346mod list_generated_templates;
347
348mod list_hook_results;
349
350mod list_imports;
351
352mod list_resource_scan_related_resources;
353
354mod list_resource_scan_resources;
355
356mod list_resource_scans;
357
358mod list_stack_instance_resource_drifts;
359
360mod list_stack_instances;
361
362mod list_stack_refactor_actions;
363
364mod list_stack_refactors;
365
366mod list_stack_resources;
367
368mod list_stack_set_auto_deployment_targets;
369
370mod list_stack_set_operation_results;
371
372mod list_stack_set_operations;
373
374mod list_stack_sets;
375
376mod list_stacks;
377
378mod list_type_registrations;
379
380mod list_type_versions;
381
382mod list_types;
383
384mod publish_type;
385
386mod record_handler_progress;
387
388mod register_publisher;
389
390mod register_type;
391
392mod rollback_stack;
393
394mod set_stack_policy;
395
396mod set_type_configuration;
397
398mod set_type_default_version;
399
400mod signal_resource;
401
402mod start_resource_scan;
403
404mod stop_stack_set_operation;
405
406mod test_type;
407
408mod update_generated_template;
409
410mod update_stack;
411
412mod update_stack_instances;
413
414mod update_stack_set;
415
416mod update_termination_protection;
417
418mod validate_template;