Struct CreateAppInput

#[non_exhaustive]
pub struct CreateAppInput {
    pub stack_id: Option<String>,
    pub shortname: Option<String>,
    pub name: Option<String>,
    pub description: Option<String>,
    pub data_sources: Option<Vec<DataSource>>,
    pub type: Option<AppType>,
    pub app_source: Option<Source>,
    pub domains: Option<Vec<String>>,
    pub enable_ssl: Option<bool>,
    pub ssl_configuration: Option<SslConfiguration>,
    pub attributes: Option<HashMap<AppAttributesKeys, String>>,
    pub environment: Option<Vec<EnvironmentVariable>>,
}

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

stack_id: Option<String>

The stack ID.

shortname: Option<String>

The app's short name.

name: Option<String>

The app name.

description: Option<String>

A description of the app.

data_sources: Option<Vec<DataSource>>

The app's data source.

type: Option<AppType>

The app type. Each supported type is associated with a particular layer. For example, PHP applications are associated with a PHP layer. OpsWorks Stacks deploys an application to those instances that are members of the corresponding layer. If your app isn't one of the standard types, or you prefer to implement your own Deploy recipes, specify other.

app_source: Option<Source>

A Source object that specifies the app repository.

domains: Option<Vec<String>>

The app virtual host settings, with multiple domains separated by commas. For example: 'www.example.com, example.com'

enable_ssl: Option<bool>

Whether to enable SSL for the app.

ssl_configuration: Option<SslConfiguration>

An SslConfiguration object with the SSL configuration.

attributes: Option<HashMap<AppAttributesKeys, String>>

One or more user-defined key/value pairs to be added to the stack attributes.

environment: Option<Vec<EnvironmentVariable>>

An array of EnvironmentVariable objects that specify environment variables to be associated with the app. After you deploy the app, these variables are defined on the associated app server instance. For more information, see Environment Variables.

There is no specific limit on the number of environment variables. However, the size of the associated data structure - which includes the variables' names, values, and protected flag values - cannot exceed 20 KB. This limit should accommodate most if not all use cases. Exceeding it will cause an exception with the message, "Environment: is too large (maximum is 20KB)."

If you have specified one or more environment variables, you cannot modify the stack's Chef version.

Implementations

impl CreateAppInput

pub fn stack_id(&self) -> Option<&str>

The stack ID.

pub fn shortname(&self) -> Option<&str>

The app's short name.

pub fn name(&self) -> Option<&str>

The app name.

pub fn description(&self) -> Option<&str>

A description of the app.

pub fn data_sources(&self) -> &[DataSource]

The app's data source.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .data_sources.is_none().

pub fn type(&self) -> Option<&AppType>

The app type. Each supported type is associated with a particular layer. For example, PHP applications are associated with a PHP layer. OpsWorks Stacks deploys an application to those instances that are members of the corresponding layer. If your app isn't one of the standard types, or you prefer to implement your own Deploy recipes, specify other.

pub fn app_source(&self) -> Option<&Source>

A Source object that specifies the app repository.

pub fn domains(&self) -> &[String]

The app virtual host settings, with multiple domains separated by commas. For example: 'www.example.com, example.com'

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .domains.is_none().

pub fn enable_ssl(&self) -> Option<bool>

Whether to enable SSL for the app.

pub fn ssl_configuration(&self) -> Option<&SslConfiguration>

An SslConfiguration object with the SSL configuration.

pub fn attributes(&self) -> Option<&HashMap<AppAttributesKeys, String>>

One or more user-defined key/value pairs to be added to the stack attributes.

pub fn environment(&self) -> &[EnvironmentVariable]

An array of EnvironmentVariable objects that specify environment variables to be associated with the app. After you deploy the app, these variables are defined on the associated app server instance. For more information, see Environment Variables.

There is no specific limit on the number of environment variables. However, the size of the associated data structure - which includes the variables' names, values, and protected flag values - cannot exceed 20 KB. This limit should accommodate most if not all use cases. Exceeding it will cause an exception with the message, "Environment: is too large (maximum is 20KB)."

If you have specified one or more environment variables, you cannot modify the stack's Chef version.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .environment.is_none().

impl CreateAppInput

pub fn builder() -> CreateAppInputBuilder

Creates a new builder-style object to manufacture CreateAppInput.

Trait Implementations

impl Clone for CreateAppInput

fn clone(&self) -> CreateAppInput

Returns a duplicate of the value.

const fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for CreateAppInput

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq for CreateAppInput

fn eq(&self, other: &CreateAppInput) -> bool

Tests for self and other values to be equal, and is used by ==.

const fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for CreateAppInput