//! <p>AppConfig Data provides the data plane APIs your application uses to retrieve configuration data.
//! Here's how it works:</p>
//! <p>Your application retrieves configuration data by first establishing a configuration
//! session using the AppConfig Data <a>StartConfigurationSession</a> API action. Your session's
//! client then makes periodic calls to <a>GetLatestConfiguration</a> to check for
//! and retrieve the latest data available.</p>
//! <p>When calling <code>StartConfigurationSession</code>, your code sends the following
//! information:</p>
//! <ul>
//! <li>
//! <p>Identifiers (ID or name) of an AppConfig application, environment, and
//! configuration profile that the session tracks.</p>
//! </li>
//! <li>
//! <p>(Optional) The minimum amount of time the session's client must wait between calls
//! to <code>GetLatestConfiguration</code>.</p>
//! </li>
//! </ul>
//! <p>In response, AppConfig provides an <code>InitialConfigurationToken</code> to be given to
//! the session's client and used the first time it calls <code>GetLatestConfiguration</code>
//! for that session.</p>
//! <p>When calling <code>GetLatestConfiguration</code>, your client code sends the most recent
//! <code>ConfigurationToken</code> value it has and receives in response:</p>
//! <ul>
//! <li>
//! <p>
//! <code>NextPollConfigurationToken</code>: the <code>ConfigurationToken</code> value
//! to use on the next call to <code>GetLatestConfiguration</code>.</p>
//! </li>
//! <li>
//! <p>
//! <code>NextPollIntervalInSeconds</code>: the duration the client should wait before
//! making its next call to <code>GetLatestConfiguration</code>. This duration may vary
//! over the course of the session, so it should be used instead of the value sent on the
//! <code>StartConfigurationSession</code> call.</p>
//! </li>
//! <li>
//! <p>The configuration: the latest data intended for the session. This may be empty if
//! the client already has the latest version of the configuration.</p>
//! </li>
//! </ul>
//! <p>For more information and to view example CLI commands that show how to retrieve a
//! configuration using the AppConfig Data <code>StartConfigurationSession</code> and
//! <code>GetLatestConfiguration</code> API actions, see <a href="http://docs.aws.amazon.com/appconfig/latest/userguide/appconfig-retrieving-the-configuration">Receiving the
//! configuration</a> in the <i>AppConfig User Guide</i>.</p>
//!
//! # Crate Organization
//!
//! The entry point for most customers will be [`Client`]. [`Client`] exposes one method for each API offered
//! by the service.
//!
//! Some APIs require complex or nested arguments. These exist in [`model`](crate::model).
//!
//! Lastly, errors that can be returned by the service are contained within [`error`]. [`Error`] defines a meta
//! error encompassing all possible errors that can be returned by the service.
//!
//! The other modules within this crate are not required for normal usage.
// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
pub use Error;
pub use Config;
/// Client and fluent builders for calling the service.
/// Configuration for the service.
/// Endpoint resolution functionality
/// All error types that operations can return. Documentation on these types is copied from the model.
/// Input structures for operations. Documentation on these types is copied from the model.
/// Data structures used by operation inputs/outputs. Documentation on these types is copied from the model.
/// All operations that this crate can perform.
/// Output structures for operations. Documentation on these types is copied from the model.
/// Data primitives referenced by other data types.
/// Endpoints standard library functions
/// Crate version number.
pub static PKG_VERSION: &str = env!;
pub use Endpoint;
static API_METADATA: ApiMetadata =
new;
pub use Credentials;
pub use AppName;
pub use Region;
pub use Client;