aws-sdk-route53resolver 1.111.0

// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
#[derive(Debug)]
pub(crate) struct Handle {
    pub(crate) conf: crate::Config,
    #[allow(dead_code)] // unused when a service does not provide any operations
    pub(crate) runtime_plugins: ::aws_smithy_runtime_api::client::runtime_plugin::RuntimePlugins,
}

/// Client for Amazon Route 53 Resolver
///
/// Client for invoking operations on Amazon Route 53 Resolver. Each operation on Amazon Route 53 Resolver is a method on this
/// this struct. `.send()` MUST be invoked on the generated operations to dispatch the request to the service.
/// ## Constructing a `Client`
///
/// A [`Config`] is required to construct a client. For most use cases, the [`aws-config`]
/// crate should be used to automatically resolve this config using
/// [`aws_config::load_from_env()`], since this will resolve an [`SdkConfig`] which can be shared
/// across multiple different AWS SDK clients. This config resolution process can be customized
/// by calling [`aws_config::from_env()`] instead, which returns a [`ConfigLoader`] that uses
/// the [builder pattern] to customize the default config.
///
/// In the simplest case, creating a client looks as follows:
/// ```rust,no_run
/// # async fn wrapper() {
/// let config = aws_config::load_from_env().await;
/// let client = aws_sdk_route53resolver::Client::new(&config);
/// # }
/// ```
///
/// Occasionally, SDKs may have additional service-specific values that can be set on the [`Config`] that
/// is absent from [`SdkConfig`], or slightly different settings for a specific client may be desired.
/// The [`Builder`](crate::config::Builder) struct implements `From<&SdkConfig>`, so setting these specific settings can be
/// done as follows:
///
/// ```rust,no_run
/// # async fn wrapper() {
/// let sdk_config = ::aws_config::load_from_env().await;
/// let config = aws_sdk_route53resolver::config::Builder::from(&sdk_config)
/// # /*
///     .some_service_specific_setting("value")
/// # */
///     .build();
/// # }
/// ```
///
/// See the [`aws-config` docs] and [`Config`] for more information on customizing configuration.
///
/// _Note:_ Client construction is expensive due to connection thread pool initialization, and should
/// be done once at application start-up.
///
/// [`Config`]: crate::Config
/// [`ConfigLoader`]: https://docs.rs/aws-config/*/aws_config/struct.ConfigLoader.html
/// [`SdkConfig`]: https://docs.rs/aws-config/*/aws_config/struct.SdkConfig.html
/// [`aws-config` docs]: https://docs.rs/aws-config/*
/// [`aws-config`]: https://crates.io/crates/aws-config
/// [`aws_config::from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.from_env.html
/// [`aws_config::load_from_env()`]: https://docs.rs/aws-config/*/aws_config/fn.load_from_env.html
/// [builder pattern]: https://rust-lang.github.io/api-guidelines/type-safety.html#builders-enable-construction-of-complex-values-c-builder
/// # Using the `Client`
///
/// A client has a function for every operation that can be performed by the service.
/// For example, the [`AssociateFirewallRuleGroup`](crate::operation::associate_firewall_rule_group) operation has
/// a [`Client::associate_firewall_rule_group`], function which returns a builder for that operation.
/// The fluent builder ultimately has a `send()` function that returns an async future that
/// returns a result, as illustrated below:
///
/// ```rust,ignore
/// let result = client.associate_firewall_rule_group()
///     .creator_request_id("example")
///     .send()
///     .await;
/// ```
///
/// The underlying HTTP requests that get made by this can be modified with the `customize_operation`
/// function on the fluent builder. See the [`customize`](crate::client::customize) module for more
/// information.
#[derive(::std::clone::Clone, ::std::fmt::Debug)]
pub struct Client {
    handle: ::std::sync::Arc<Handle>,
}

impl Client {
    /// Creates a new client from the service [`Config`](crate::Config).
    ///
    /// # Panics
    ///
    /// This method will panic in the following cases:
    ///
    /// - Retries or timeouts are enabled without a `sleep_impl` configured.
    /// - Identity caching is enabled without a `sleep_impl` and `time_source` configured.
    /// - No `behavior_version` is provided.
    ///
    /// The panic message for each of these will have instructions on how to resolve them.
    #[track_caller]
    pub fn from_conf(conf: crate::Config) -> Self {
        let handle = Handle {
            conf: conf.clone(),
            runtime_plugins: crate::config::base_client_runtime_plugins(conf),
        };
        if let Err(err) = Self::validate_config(&handle) {
            panic!("Invalid client configuration: {err}");
        }
        Self {
            handle: ::std::sync::Arc::new(handle),
        }
    }

    /// Returns the client's configuration.
    pub fn config(&self) -> &crate::Config {
        &self.handle.conf
    }

    fn validate_config(handle: &Handle) -> ::std::result::Result<(), ::aws_smithy_runtime_api::box_error::BoxError> {
        let mut cfg = ::aws_smithy_types::config_bag::ConfigBag::base();
        handle
            .runtime_plugins
            .apply_client_configuration(&mut cfg)?
            .validate_base_client_config(&cfg)?;
        Ok(())
    }
}

impl Client {
    /// Creates a new client from an [SDK Config](::aws_types::sdk_config::SdkConfig).
    ///
    /// # Panics
    ///
    /// - This method will panic if the `sdk_config` is missing an async sleep implementation. If you experience this panic, set
    ///   the `sleep_impl` on the Config passed into this function to fix it.
    /// - This method will panic if the `sdk_config` is missing an HTTP connector. If you experience this panic, set the
    ///   `http_connector` on the Config passed into this function to fix it.
    /// - 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.
    #[track_caller]
    pub fn new(sdk_config: &::aws_types::sdk_config::SdkConfig) -> Self {
        Self::from_conf(sdk_config.into())
    }
}

mod associate_firewall_rule_group;

mod associate_resolver_endpoint_ip_address;

mod associate_resolver_query_log_config;

mod associate_resolver_rule;

mod batch_create_firewall_rule;

mod batch_delete_firewall_rule;

mod batch_update_firewall_rule;

mod create_firewall_domain_list;

mod create_firewall_rule;

mod create_firewall_rule_group;

mod create_outpost_resolver;

mod create_resolver_endpoint;

mod create_resolver_query_log_config;

mod create_resolver_rule;

/// Operation customization and supporting types.
///
/// The underlying HTTP requests made during an operation can be customized
/// by calling the `customize()` method on the builder returned from a client
/// operation call. For example, this can be used to add an additional HTTP header:
///
/// ```ignore
/// # async fn wrapper() -> ::std::result::Result<(), aws_sdk_route53resolver::Error> {
/// # let client: aws_sdk_route53resolver::Client = unimplemented!();
/// use ::http_1x::header::{HeaderName, HeaderValue};
///
/// let result = client.associate_firewall_rule_group()
///     .customize()
///     .mutate_request(|req| {
///         // Add `x-example-header` with value
///         req.headers_mut()
///             .insert(
///                 HeaderName::from_static("x-example-header"),
///                 HeaderValue::from_static("1"),
///             );
///     })
///     .send()
///     .await;
/// # }
/// ```
pub mod customize;

mod delete_firewall_domain_list;

mod delete_firewall_rule;

mod delete_firewall_rule_group;

mod delete_outpost_resolver;

mod delete_resolver_endpoint;

mod delete_resolver_query_log_config;

mod delete_resolver_rule;

mod disassociate_firewall_rule_group;

mod disassociate_resolver_endpoint_ip_address;

mod disassociate_resolver_query_log_config;

mod disassociate_resolver_rule;

mod get_firewall_config;

mod get_firewall_domain_list;

mod get_firewall_rule_group;

mod get_firewall_rule_group_association;

mod get_firewall_rule_group_policy;

mod get_outpost_resolver;

mod get_resolver_config;

mod get_resolver_dnssec_config;

mod get_resolver_endpoint;

mod get_resolver_query_log_config;

mod get_resolver_query_log_config_association;

mod get_resolver_query_log_config_policy;

mod get_resolver_rule;

mod get_resolver_rule_association;

mod get_resolver_rule_policy;

mod import_firewall_domains;

mod list_firewall_configs;

mod list_firewall_domain_lists;

mod list_firewall_domains;

mod list_firewall_rule_group_associations;

mod list_firewall_rule_groups;

mod list_firewall_rule_types;

mod list_firewall_rules;

mod list_outpost_resolvers;

mod list_resolver_configs;

mod list_resolver_dnssec_configs;

mod list_resolver_endpoint_ip_addresses;

mod list_resolver_endpoints;

mod list_resolver_query_log_config_associations;

mod list_resolver_query_log_configs;

mod list_resolver_rule_associations;

mod list_resolver_rules;

mod list_tags_for_resource;

mod put_firewall_rule_group_policy;

mod put_resolver_query_log_config_policy;

mod put_resolver_rule_policy;

mod tag_resource;

mod untag_resource;

mod update_firewall_config;

mod update_firewall_domains;

mod update_firewall_rule;

mod update_firewall_rule_group_association;

mod update_outpost_resolver;

mod update_resolver_config;

mod update_resolver_dnssec_config;

mod update_resolver_endpoint;

mod update_resolver_rule;