#[non_exhaustive]pub struct UpdateStackInput {Show 18 fields
pub stack_id: Option<String>,
pub name: Option<String>,
pub attributes: Option<HashMap<StackAttributesKeys, String>>,
pub service_role_arn: Option<String>,
pub default_instance_profile_arn: Option<String>,
pub default_os: Option<String>,
pub hostname_theme: Option<String>,
pub default_availability_zone: Option<String>,
pub default_subnet_id: Option<String>,
pub custom_json: Option<String>,
pub configuration_manager: Option<StackConfigurationManager>,
pub chef_configuration: Option<ChefConfiguration>,
pub use_custom_cookbooks: Option<bool>,
pub custom_cookbooks_source: Option<Source>,
pub default_ssh_key_name: Option<String>,
pub default_root_device_type: Option<RootDeviceType>,
pub use_opsworks_security_groups: Option<bool>,
pub agent_version: Option<String>,
}
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.stack_id: Option<String>
The stack ID.
name: Option<String>
The stack's new name. Stack names can be a maximum of 64 characters.
attributes: Option<HashMap<StackAttributesKeys, String>>
One or more user-defined key-value pairs to be added to the stack attributes.
service_role_arn: Option<String>
Do not use this parameter. You cannot update a stack's service role.
default_instance_profile_arn: Option<String>
The ARN of an IAM profile that is the default profile for all of the stack's EC2 instances. For more information about IAM ARNs, see Using Identifiers.
default_os: Option<String>
The stack's operating system, which must be set to one of the following:
-
A supported Linux operating system: An Amazon Linux version, such as
Amazon Linux 2
,Amazon Linux 2018.03
,Amazon Linux 2017.09
,Amazon Linux 2017.03
,Amazon Linux 2016.09
,Amazon Linux 2016.03
,Amazon Linux 2015.09
, orAmazon Linux 2015.03
. -
A supported Ubuntu operating system, such as
Ubuntu 18.04 LTS
,Ubuntu 16.04 LTS
,Ubuntu 14.04 LTS
, orUbuntu 12.04 LTS
. -
CentOS Linux 7
-
Red Hat Enterprise Linux 7
-
A supported Windows operating system, such as
Microsoft Windows Server 2012 R2 Base
,Microsoft Windows Server 2012 R2 with SQL Server Express
,Microsoft Windows Server 2012 R2 with SQL Server Standard
, orMicrosoft Windows Server 2012 R2 with SQL Server Web
. -
A custom AMI:
Custom
. You specify the custom AMI you want to use when you create instances. For more information about how to use custom AMIs with OpsWorks, see Using Custom AMIs.
The default option is the stack's current operating system. Not all operating systems are supported with all versions of Chef. For more information about supported operating systems, see OpsWorks Stacks Operating Systems.
hostname_theme: Option<String>
The stack's new host name theme, with spaces replaced by underscores. The theme is used to generate host names for the stack's instances. By default, HostnameTheme
is set to Layer_Dependent
, which creates host names by appending integers to the layer's short name. The other themes are:
-
Baked_Goods
-
Clouds
-
Europe_Cities
-
Fruits
-
Greek_Deities_and_Titans
-
Legendary_creatures_from_Japan
-
Planets_and_Moons
-
Roman_Deities
-
Scottish_Islands
-
US_Cities
-
Wild_Cats
To obtain a generated host name, call GetHostNameSuggestion
, which returns a host name based on the current theme.
default_availability_zone: Option<String>
The stack's default Availability Zone, which must be in the stack's region. For more information, see Regions and Endpoints. If you also specify a value for DefaultSubnetId
, the subnet must be in the same zone. For more information, see CreateStack
.
default_subnet_id: Option<String>
The stack's default VPC subnet ID. This parameter is required if you specify a value for the VpcId
parameter. All instances are launched into this subnet unless you specify otherwise when you create the instance. If you also specify a value for DefaultAvailabilityZone
, the subnet must be in that zone. For information on default values and when this parameter is required, see the VpcId
parameter description.
custom_json: Option<String>
A string that contains user-defined, custom JSON. It can be used to override the corresponding default stack configuration JSON values or to pass data to recipes. The string should be in the following format:
"{\"key1\": \"value1\", \"key2\": \"value2\",...}"
For more information about custom JSON, see Use Custom JSON to Modify the Stack Configuration Attributes.
configuration_manager: Option<StackConfigurationManager>
The configuration manager. When you update a stack, we recommend that you use the configuration manager to specify the Chef version: 12, 11.10, or 11.4 for Linux stacks, or 12.2 for Windows stacks. The default value for Linux stacks is currently 12.
chef_configuration: Option<ChefConfiguration>
A ChefConfiguration
object that specifies whether to enable Berkshelf and the Berkshelf version on Chef 11.10 stacks. For more information, see Create a New Stack.
use_custom_cookbooks: Option<bool>
Whether the stack uses custom cookbooks.
custom_cookbooks_source: Option<Source>
Contains the information required to retrieve an app or cookbook from a repository. For more information, see Adding Apps or Cookbooks and Recipes.
default_ssh_key_name: Option<String>
A default Amazon EC2 key-pair name. The default value is none
. If you specify a key-pair name, OpsWorks Stacks installs the public key on the instance and you can use the private key with an SSH client to log in to the instance. For more information, see Using SSH to Communicate with an Instance and Managing SSH Access. You can override this setting by specifying a different key pair, or no key pair, when you create an instance.
default_root_device_type: Option<RootDeviceType>
The default root device type. This value is used by default for all instances in the stack, but you can override it when you create an instance. For more information, see Storage for the Root Device.
use_opsworks_security_groups: Option<bool>
Whether to associate the OpsWorks Stacks built-in security groups with the stack's layers.
OpsWorks Stacks provides a standard set of built-in security groups, one for each layer, which are associated with layers by default. UseOpsworksSecurityGroups
allows you to provide your own custom security groups instead of using the built-in groups. UseOpsworksSecurityGroups
has the following settings:
-
True - OpsWorks Stacks automatically associates the appropriate built-in security group with each layer (default setting). You can associate additional security groups with a layer after you create it, but you cannot delete the built-in security group.
-
False - OpsWorks Stacks does not associate built-in security groups with layers. You must create appropriate EC2 security groups and associate a security group with each layer that you create. However, you can still manually associate a built-in security group with a layer on. Custom security groups are required only for those layers that need custom settings.
For more information, see Create a New Stack.
agent_version: Option<String>
The default OpsWorks Stacks agent version. You have the following options:
-
Auto-update - Set this parameter to
LATEST
. OpsWorks Stacks automatically installs new agent versions on the stack's instances as soon as they are available. -
Fixed version - Set this parameter to your preferred agent version. To update the agent version, you must edit the stack configuration and specify a new version. OpsWorks Stacks installs that version on the stack's instances.
The default setting is LATEST
. To specify an agent version, you must use the complete version number, not the abbreviated number shown on the console. For a list of available agent version numbers, call DescribeAgentVersions
. AgentVersion cannot be set to Chef 12.2.
You can also specify an agent version when you create or update an instance, which overrides the stack's default setting.
Implementations§
Source§impl UpdateStackInput
impl UpdateStackInput
Sourcepub fn name(&self) -> Option<&str>
pub fn name(&self) -> Option<&str>
The stack's new name. Stack names can be a maximum of 64 characters.
Sourcepub fn attributes(&self) -> Option<&HashMap<StackAttributesKeys, String>>
pub fn attributes(&self) -> Option<&HashMap<StackAttributesKeys, String>>
One or more user-defined key-value pairs to be added to the stack attributes.
Sourcepub fn service_role_arn(&self) -> Option<&str>
pub fn service_role_arn(&self) -> Option<&str>
Do not use this parameter. You cannot update a stack's service role.
Sourcepub fn default_instance_profile_arn(&self) -> Option<&str>
pub fn default_instance_profile_arn(&self) -> Option<&str>
The ARN of an IAM profile that is the default profile for all of the stack's EC2 instances. For more information about IAM ARNs, see Using Identifiers.
Sourcepub fn default_os(&self) -> Option<&str>
pub fn default_os(&self) -> Option<&str>
The stack's operating system, which must be set to one of the following:
-
A supported Linux operating system: An Amazon Linux version, such as
Amazon Linux 2
,Amazon Linux 2018.03
,Amazon Linux 2017.09
,Amazon Linux 2017.03
,Amazon Linux 2016.09
,Amazon Linux 2016.03
,Amazon Linux 2015.09
, orAmazon Linux 2015.03
. -
A supported Ubuntu operating system, such as
Ubuntu 18.04 LTS
,Ubuntu 16.04 LTS
,Ubuntu 14.04 LTS
, orUbuntu 12.04 LTS
. -
CentOS Linux 7
-
Red Hat Enterprise Linux 7
-
A supported Windows operating system, such as
Microsoft Windows Server 2012 R2 Base
,Microsoft Windows Server 2012 R2 with SQL Server Express
,Microsoft Windows Server 2012 R2 with SQL Server Standard
, orMicrosoft Windows Server 2012 R2 with SQL Server Web
. -
A custom AMI:
Custom
. You specify the custom AMI you want to use when you create instances. For more information about how to use custom AMIs with OpsWorks, see Using Custom AMIs.
The default option is the stack's current operating system. Not all operating systems are supported with all versions of Chef. For more information about supported operating systems, see OpsWorks Stacks Operating Systems.
Sourcepub fn hostname_theme(&self) -> Option<&str>
pub fn hostname_theme(&self) -> Option<&str>
The stack's new host name theme, with spaces replaced by underscores. The theme is used to generate host names for the stack's instances. By default, HostnameTheme
is set to Layer_Dependent
, which creates host names by appending integers to the layer's short name. The other themes are:
-
Baked_Goods
-
Clouds
-
Europe_Cities
-
Fruits
-
Greek_Deities_and_Titans
-
Legendary_creatures_from_Japan
-
Planets_and_Moons
-
Roman_Deities
-
Scottish_Islands
-
US_Cities
-
Wild_Cats
To obtain a generated host name, call GetHostNameSuggestion
, which returns a host name based on the current theme.
Sourcepub fn default_availability_zone(&self) -> Option<&str>
pub fn default_availability_zone(&self) -> Option<&str>
The stack's default Availability Zone, which must be in the stack's region. For more information, see Regions and Endpoints. If you also specify a value for DefaultSubnetId
, the subnet must be in the same zone. For more information, see CreateStack
.
Sourcepub fn default_subnet_id(&self) -> Option<&str>
pub fn default_subnet_id(&self) -> Option<&str>
The stack's default VPC subnet ID. This parameter is required if you specify a value for the VpcId
parameter. All instances are launched into this subnet unless you specify otherwise when you create the instance. If you also specify a value for DefaultAvailabilityZone
, the subnet must be in that zone. For information on default values and when this parameter is required, see the VpcId
parameter description.
Sourcepub fn custom_json(&self) -> Option<&str>
pub fn custom_json(&self) -> Option<&str>
A string that contains user-defined, custom JSON. It can be used to override the corresponding default stack configuration JSON values or to pass data to recipes. The string should be in the following format:
"{\"key1\": \"value1\", \"key2\": \"value2\",...}"
For more information about custom JSON, see Use Custom JSON to Modify the Stack Configuration Attributes.
Sourcepub fn configuration_manager(&self) -> Option<&StackConfigurationManager>
pub fn configuration_manager(&self) -> Option<&StackConfigurationManager>
The configuration manager. When you update a stack, we recommend that you use the configuration manager to specify the Chef version: 12, 11.10, or 11.4 for Linux stacks, or 12.2 for Windows stacks. The default value for Linux stacks is currently 12.
Sourcepub fn chef_configuration(&self) -> Option<&ChefConfiguration>
pub fn chef_configuration(&self) -> Option<&ChefConfiguration>
A ChefConfiguration
object that specifies whether to enable Berkshelf and the Berkshelf version on Chef 11.10 stacks. For more information, see Create a New Stack.
Sourcepub fn use_custom_cookbooks(&self) -> Option<bool>
pub fn use_custom_cookbooks(&self) -> Option<bool>
Whether the stack uses custom cookbooks.
Sourcepub fn custom_cookbooks_source(&self) -> Option<&Source>
pub fn custom_cookbooks_source(&self) -> Option<&Source>
Contains the information required to retrieve an app or cookbook from a repository. For more information, see Adding Apps or Cookbooks and Recipes.
Sourcepub fn default_ssh_key_name(&self) -> Option<&str>
pub fn default_ssh_key_name(&self) -> Option<&str>
A default Amazon EC2 key-pair name. The default value is none
. If you specify a key-pair name, OpsWorks Stacks installs the public key on the instance and you can use the private key with an SSH client to log in to the instance. For more information, see Using SSH to Communicate with an Instance and Managing SSH Access. You can override this setting by specifying a different key pair, or no key pair, when you create an instance.
Sourcepub fn default_root_device_type(&self) -> Option<&RootDeviceType>
pub fn default_root_device_type(&self) -> Option<&RootDeviceType>
The default root device type. This value is used by default for all instances in the stack, but you can override it when you create an instance. For more information, see Storage for the Root Device.
Sourcepub fn use_opsworks_security_groups(&self) -> Option<bool>
pub fn use_opsworks_security_groups(&self) -> Option<bool>
Whether to associate the OpsWorks Stacks built-in security groups with the stack's layers.
OpsWorks Stacks provides a standard set of built-in security groups, one for each layer, which are associated with layers by default. UseOpsworksSecurityGroups
allows you to provide your own custom security groups instead of using the built-in groups. UseOpsworksSecurityGroups
has the following settings:
-
True - OpsWorks Stacks automatically associates the appropriate built-in security group with each layer (default setting). You can associate additional security groups with a layer after you create it, but you cannot delete the built-in security group.
-
False - OpsWorks Stacks does not associate built-in security groups with layers. You must create appropriate EC2 security groups and associate a security group with each layer that you create. However, you can still manually associate a built-in security group with a layer on. Custom security groups are required only for those layers that need custom settings.
For more information, see Create a New Stack.
Sourcepub fn agent_version(&self) -> Option<&str>
pub fn agent_version(&self) -> Option<&str>
The default OpsWorks Stacks agent version. You have the following options:
-
Auto-update - Set this parameter to
LATEST
. OpsWorks Stacks automatically installs new agent versions on the stack's instances as soon as they are available. -
Fixed version - Set this parameter to your preferred agent version. To update the agent version, you must edit the stack configuration and specify a new version. OpsWorks Stacks installs that version on the stack's instances.
The default setting is LATEST
. To specify an agent version, you must use the complete version number, not the abbreviated number shown on the console. For a list of available agent version numbers, call DescribeAgentVersions
. AgentVersion cannot be set to Chef 12.2.
You can also specify an agent version when you create or update an instance, which overrides the stack's default setting.
Source§impl UpdateStackInput
impl UpdateStackInput
Sourcepub fn builder() -> UpdateStackInputBuilder
pub fn builder() -> UpdateStackInputBuilder
Creates a new builder-style object to manufacture UpdateStackInput
.
Trait Implementations§
Source§impl Clone for UpdateStackInput
impl Clone for UpdateStackInput
Source§fn clone(&self) -> UpdateStackInput
fn clone(&self) -> UpdateStackInput
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for UpdateStackInput
impl Debug for UpdateStackInput
Source§impl PartialEq for UpdateStackInput
impl PartialEq for UpdateStackInput
impl StructuralPartialEq for UpdateStackInput
Auto Trait Implementations§
impl Freeze for UpdateStackInput
impl RefUnwindSafe for UpdateStackInput
impl Send for UpdateStackInput
impl Sync for UpdateStackInput
impl Unpin for UpdateStackInput
impl UnwindSafe for UpdateStackInput
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left
is true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left(&self)
returns true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the foreground set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red()
and
green()
, which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg()
:
use yansi::{Paint, Color};
painted.fg(Color::White);
Set foreground color to white using white()
.
use yansi::Paint;
painted.white();
Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the background set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red()
and
on_green()
, which have the same functionality but
are pithier.
§Example
Set background color to red using fg()
:
use yansi::{Paint, Color};
painted.bg(Color::Red);
Set background color to red using on_red()
.
use yansi::Paint;
painted.on_red();
Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute
value
.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold()
and
underline()
, which have the same functionality
but are pithier.
§Example
Make text bold using attr()
:
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);
Make text bold using using bold()
.
use yansi::Paint;
painted.bold();
Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi
Quirk
value
.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask()
and
wrap()
, which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk()
:
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);
Enable wrapping using wrap()
.
use yansi::Paint;
painted.wrap();
Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.
fn clear(&self) -> Painted<&T>
resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition
value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted
only when both stdout
and stderr
are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);