Attaches the specified storage volume to the specified instance.
oci compute volume-attachment attach [OPTIONS]
The OCID of the instance.
The type of volume. The only supported value are "iscsi" and "paravirtualized".
Accepted values are:
emulated, iscsi, paravirtualized, service_determined
The OCID of the volume.
The device name.
A user-friendly name. Does not have to be unique, and it cannot be changed. Avoid entering confidential information.
Provide input to this command as a JSON document from a file using the file://path-to/file syntax.
--generate-full-command-json-input option can be used to generate a sample json file to be used with this command option. The key names are pre-populated and match the command option names (converted to camelCase format, e.g. compartment-id --> compartmentId), while the values of the keys need to be populated by the user before using the sample file as an input to this command. For any command option that accepts multiple values, the value of the key can be a JSON array.
Options can still be provided on the command line. If an option exists in both the JSON document and the command line then the command line specified value will be used.
For examples on usage of this option, please see our "using CLI with advanced JSON options" link: https://docs.cloud.oracle.com/iaas/Content/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
Whether the attachment was created in read-only mode.
Whether the attachment should be created in shareable mode. If an attachment is created in shareable mode, then other instances can attach the same volume, provided that they also create their attachments in shareable mode. Only certain volume types can be attached in shareable mode. Defaults to false if not specified.
The maximum time to wait for the resource to reach the lifecycle state defined by
--wait-for-state. Defaults to 1200 seconds.
This operation creates, modifies or deletes a resource that has a defined lifecycle state. Specify this option to perform the action and then wait until the resource reaches a given lifecycle state. Multiple states can be specified, returning on the first state. For example,
--wait-for-state FAILED would return on whichever lifecycle state is reached first. If timeout is reached, a return code of 2 is returned. For any other error, a return code of 1 is returned.
Accepted values are:
ATTACHED, ATTACHING, DETACHED, DETACHING
--wait-interval-seconds to see whether the resource to see if it has reached the lifecycle state defined by
--wait-for-state. Defaults to 30 seconds.
oci --help for help on global parameters.