Export Server Engine Attribute
opsworkscm_export_server_engine_attribute | R Documentation |
Exports a specified server engine attribute as a base64-encoded string¶
Description¶
Exports a specified server engine attribute as a base64-encoded string. For example, you can export user data that you can use in EC2 to associate nodes with a server.
This operation is synchronous.
A ValidationException
is raised when parameters of the request are not
valid. A ResourceNotFoundException
is thrown when the server does not
exist. An InvalidStateException
is thrown when the server is in any of
the following states: CREATING, TERMINATED, FAILED or DELETING.
Usage¶
Arguments¶
ExportAttributeName
[required] The name of the export attribute. Currently, the supported export attribute is
Userdata
. This exports a user data script that includes parameters and values provided in theInputAttributes
list.ServerName
[required] The name of the server from which you are exporting the attribute.
InputAttributes
The list of engine attributes. The list type is
EngineAttribute
. AnEngineAttribute
list item is a pair that includes an attribute name and its value. For theUserdata
ExportAttributeName, the following are supported engine attribute names.RunList In Chef, a list of roles or recipes that are run in the specified order. In Puppet, this parameter is ignored.
OrganizationName In Chef, an organization name. AWS OpsWorks for Chef Automate always creates the organization
default
. In Puppet, this parameter is ignored.NodeEnvironment In Chef, a node environment (for example, development, staging, or one-box). In Puppet, this parameter is ignored.
NodeClientVersion In Chef, the version of the Chef engine (three numbers separated by dots, such as 13.8.5). If this attribute is empty, OpsWorks for Chef Automate uses the most current version. In Puppet, this parameter is ignored.
Value¶
A list with the following syntax: