Docs Home
Oracle Cloud Infrastructure v2.17.0 published on Friday, Nov 15, 2024 by Pulumi
oci.Core.VolumeAttachment
Explore with Pulumi AI
This resource provides the Volume Attachment resource in Oracle Cloud Infrastructure Core service.
Attaches the specified storage volume to the specified instance.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testVolumeAttachment = new oci.core.VolumeAttachment("test_volume_attachment", {
attachmentType: volumeAttachmentAttachmentType,
instanceId: testInstance.id,
volumeId: testVolume.id,
device: volumeAttachmentDevice,
displayName: volumeAttachmentDisplayName,
encryptionInTransitType: volumeAttachmentEncryptionInTransitType,
isAgentAutoIscsiLoginEnabled: volumeAttachmentIsAgentAutoIscsiLoginEnabled,
isPvEncryptionInTransitEnabled: volumeAttachmentIsPvEncryptionInTransitEnabled,
isReadOnly: volumeAttachmentIsReadOnly,
isShareable: volumeAttachmentIsShareable,
useChap: volumeAttachmentUseChap,
});
import pulumi
import pulumi_oci as oci
test_volume_attachment = oci.core.VolumeAttachment("test_volume_attachment",
attachment_type=volume_attachment_attachment_type,
instance_id=test_instance["id"],
volume_id=test_volume["id"],
device=volume_attachment_device,
display_name=volume_attachment_display_name,
encryption_in_transit_type=volume_attachment_encryption_in_transit_type,
is_agent_auto_iscsi_login_enabled=volume_attachment_is_agent_auto_iscsi_login_enabled,
is_pv_encryption_in_transit_enabled=volume_attachment_is_pv_encryption_in_transit_enabled,
is_read_only=volume_attachment_is_read_only,
is_shareable=volume_attachment_is_shareable,
use_chap=volume_attachment_use_chap)
package main
import (
"github.com/pulumi/pulumi-oci/sdk/v2/go/oci/Core"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := Core.NewVolumeAttachment(ctx, "test_volume_attachment", &Core.VolumeAttachmentArgs{
AttachmentType: pulumi.Any(volumeAttachmentAttachmentType),
InstanceId: pulumi.Any(testInstance.Id),
VolumeId: pulumi.Any(testVolume.Id),
Device: pulumi.Any(volumeAttachmentDevice),
DisplayName: pulumi.Any(volumeAttachmentDisplayName),
EncryptionInTransitType: pulumi.Any(volumeAttachmentEncryptionInTransitType),
IsAgentAutoIscsiLoginEnabled: pulumi.Any(volumeAttachmentIsAgentAutoIscsiLoginEnabled),
IsPvEncryptionInTransitEnabled: pulumi.Any(volumeAttachmentIsPvEncryptionInTransitEnabled),
IsReadOnly: pulumi.Any(volumeAttachmentIsReadOnly),
IsShareable: pulumi.Any(volumeAttachmentIsShareable),
UseChap: pulumi.Any(volumeAttachmentUseChap),
})
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Oci = Pulumi.Oci;
return await Deployment.RunAsync(() =>
{
var testVolumeAttachment = new Oci.Core.VolumeAttachment("test_volume_attachment", new()
{
AttachmentType = volumeAttachmentAttachmentType,
InstanceId = testInstance.Id,
VolumeId = testVolume.Id,
Device = volumeAttachmentDevice,
DisplayName = volumeAttachmentDisplayName,
EncryptionInTransitType = volumeAttachmentEncryptionInTransitType,
IsAgentAutoIscsiLoginEnabled = volumeAttachmentIsAgentAutoIscsiLoginEnabled,
IsPvEncryptionInTransitEnabled = volumeAttachmentIsPvEncryptionInTransitEnabled,
IsReadOnly = volumeAttachmentIsReadOnly,
IsShareable = volumeAttachmentIsShareable,
UseChap = volumeAttachmentUseChap,
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.oci.Core.VolumeAttachment;
import com.pulumi.oci.Core.VolumeAttachmentArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
var testVolumeAttachment = new VolumeAttachment("testVolumeAttachment", VolumeAttachmentArgs.builder()
.attachmentType(volumeAttachmentAttachmentType)
.instanceId(testInstance.id())
.volumeId(testVolume.id())
.device(volumeAttachmentDevice)
.displayName(volumeAttachmentDisplayName)
.encryptionInTransitType(volumeAttachmentEncryptionInTransitType)
.isAgentAutoIscsiLoginEnabled(volumeAttachmentIsAgentAutoIscsiLoginEnabled)
.isPvEncryptionInTransitEnabled(volumeAttachmentIsPvEncryptionInTransitEnabled)
.isReadOnly(volumeAttachmentIsReadOnly)
.isShareable(volumeAttachmentIsShareable)
.useChap(volumeAttachmentUseChap)
.build());
}
}
resources:
testVolumeAttachment:
type: oci:Core:VolumeAttachment
name: test_volume_attachment
properties:
attachmentType: ${volumeAttachmentAttachmentType}
instanceId: ${testInstance.id}
volumeId: ${testVolume.id}
device: ${volumeAttachmentDevice}
displayName: ${volumeAttachmentDisplayName}
encryptionInTransitType: ${volumeAttachmentEncryptionInTransitType}
isAgentAutoIscsiLoginEnabled: ${volumeAttachmentIsAgentAutoIscsiLoginEnabled}
isPvEncryptionInTransitEnabled: ${volumeAttachmentIsPvEncryptionInTransitEnabled}
isReadOnly: ${volumeAttachmentIsReadOnly}
isShareable: ${volumeAttachmentIsShareable}
useChap: ${volumeAttachmentUseChap}
Create VolumeAttachment Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new VolumeAttachment(name: string, args: VolumeAttachmentArgs, opts?: CustomResourceOptions);@overload
def VolumeAttachment(resource_name: str,
args: VolumeAttachmentArgs,
opts: Optional[ResourceOptions] = None)
@overload
def VolumeAttachment(resource_name: str,
opts: Optional[ResourceOptions] = None,
attachment_type: Optional[str] = None,
instance_id: Optional[str] = None,
volume_id: Optional[str] = None,
compartment_id: Optional[str] = None,
device: Optional[str] = None,
display_name: Optional[str] = None,
encryption_in_transit_type: Optional[str] = None,
is_agent_auto_iscsi_login_enabled: Optional[bool] = None,
is_pv_encryption_in_transit_enabled: Optional[bool] = None,
is_read_only: Optional[bool] = None,
is_shareable: Optional[bool] = None,
use_chap: Optional[bool] = None)func NewVolumeAttachment(ctx *Context, name string, args VolumeAttachmentArgs, opts ...ResourceOption) (*VolumeAttachment, error)public VolumeAttachment(string name, VolumeAttachmentArgs args, CustomResourceOptions? opts = null)
public VolumeAttachment(String name, VolumeAttachmentArgs args)
public VolumeAttachment(String name, VolumeAttachmentArgs args, CustomResourceOptions options)
type: oci:Core:VolumeAttachment
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args VolumeAttachmentArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args VolumeAttachmentArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args VolumeAttachmentArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args VolumeAttachmentArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args VolumeAttachmentArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var volumeAttachmentResource = new Oci.Core.VolumeAttachment("volumeAttachmentResource", new()
{
AttachmentType = "string",
InstanceId = "string",
VolumeId = "string",
Device = "string",
DisplayName = "string",
EncryptionInTransitType = "string",
IsAgentAutoIscsiLoginEnabled = false,
IsPvEncryptionInTransitEnabled = false,
IsReadOnly = false,
IsShareable = false,
UseChap = false,
});
example, err := Core.NewVolumeAttachment(ctx, "volumeAttachmentResource", &Core.VolumeAttachmentArgs{
AttachmentType: pulumi.String("string"),
InstanceId: pulumi.String("string"),
VolumeId: pulumi.String("string"),
Device: pulumi.String("string"),
DisplayName: pulumi.String("string"),
EncryptionInTransitType: pulumi.String("string"),
IsAgentAutoIscsiLoginEnabled: pulumi.Bool(false),
IsPvEncryptionInTransitEnabled: pulumi.Bool(false),
IsReadOnly: pulumi.Bool(false),
IsShareable: pulumi.Bool(false),
UseChap: pulumi.Bool(false),
})
var volumeAttachmentResource = new VolumeAttachment("volumeAttachmentResource", VolumeAttachmentArgs.builder()
.attachmentType("string")
.instanceId("string")
.volumeId("string")
.device("string")
.displayName("string")
.encryptionInTransitType("string")
.isAgentAutoIscsiLoginEnabled(false)
.isPvEncryptionInTransitEnabled(false)
.isReadOnly(false)
.isShareable(false)
.useChap(false)
.build());
volume_attachment_resource = oci.core.VolumeAttachment("volumeAttachmentResource",
attachment_type="string",
instance_id="string",
volume_id="string",
device="string",
display_name="string",
encryption_in_transit_type="string",
is_agent_auto_iscsi_login_enabled=False,
is_pv_encryption_in_transit_enabled=False,
is_read_only=False,
is_shareable=False,
use_chap=False)
const volumeAttachmentResource = new oci.core.VolumeAttachment("volumeAttachmentResource", {
attachmentType: "string",
instanceId: "string",
volumeId: "string",
device: "string",
displayName: "string",
encryptionInTransitType: "string",
isAgentAutoIscsiLoginEnabled: false,
isPvEncryptionInTransitEnabled: false,
isReadOnly: false,
isShareable: false,
useChap: false,
});
type: oci:Core:VolumeAttachment
properties:
attachmentType: string
device: string
displayName: string
encryptionInTransitType: string
instanceId: string
isAgentAutoIscsiLoginEnabled: false
isPvEncryptionInTransitEnabled: false
isReadOnly: false
isShareable: false
useChap: false
volumeId: string
VolumeAttachment Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The VolumeAttachment resource accepts the following input properties:
- Attachment
Type string - The type of volume. The only supported values are "iscsi" and "paravirtualized".
- Instance
Id string - The OCID of the instance.
- Volume
Id string The OCID of the volume.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- Compartment
Id string - The OCID of the compartment.
- Device string
- The device name. To retrieve a list of devices for a given instance, see ListInstanceDevices.
- Display
Name string - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- Encryption
In stringTransit Type - Refer the top-level definition of encryptionInTransitType. The default value is NONE.
- Is
Agent boolAuto Iscsi Login Enabled - Whether to enable Oracle Cloud Agent to perform the iSCSI login and logout commands after the volume attach or detach operations for non multipath-enabled iSCSI attachments.
- Is
Pv boolEncryption In Transit Enabled - Whether to enable in-transit encryption for the data volume's paravirtualized attachment. The default value is false.
- Is
Read boolOnly - Whether the attachment was created in read-only mode.
- bool
- 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.
- Use
Chap bool - Whether to use CHAP authentication for the volume attachment. Defaults to false.
- Attachment
Type string - The type of volume. The only supported values are "iscsi" and "paravirtualized".
- Instance
Id string - The OCID of the instance.
- Volume
Id string The OCID of the volume.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- Compartment
Id string - The OCID of the compartment.
- Device string
- The device name. To retrieve a list of devices for a given instance, see ListInstanceDevices.
- Display
Name string - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- Encryption
In stringTransit Type - Refer the top-level definition of encryptionInTransitType. The default value is NONE.
- Is
Agent boolAuto Iscsi Login Enabled - Whether to enable Oracle Cloud Agent to perform the iSCSI login and logout commands after the volume attach or detach operations for non multipath-enabled iSCSI attachments.
- Is
Pv boolEncryption In Transit Enabled - Whether to enable in-transit encryption for the data volume's paravirtualized attachment. The default value is false.
- Is
Read boolOnly - Whether the attachment was created in read-only mode.
- bool
- 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.
- Use
Chap bool - Whether to use CHAP authentication for the volume attachment. Defaults to false.
- attachment
Type String - The type of volume. The only supported values are "iscsi" and "paravirtualized".
- instance
Id String - The OCID of the instance.
- volume
Id String The OCID of the volume.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- compartment
Id String - The OCID of the compartment.
- device String
- The device name. To retrieve a list of devices for a given instance, see ListInstanceDevices.
- display
Name String - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- encryption
In StringTransit Type - Refer the top-level definition of encryptionInTransitType. The default value is NONE.
- is
Agent BooleanAuto Iscsi Login Enabled - Whether to enable Oracle Cloud Agent to perform the iSCSI login and logout commands after the volume attach or detach operations for non multipath-enabled iSCSI attachments.
- is
Pv BooleanEncryption In Transit Enabled - Whether to enable in-transit encryption for the data volume's paravirtualized attachment. The default value is false.
- is
Read BooleanOnly - Whether the attachment was created in read-only mode.
- Boolean
- 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.
- use
Chap Boolean - Whether to use CHAP authentication for the volume attachment. Defaults to false.
- attachment
Type string - The type of volume. The only supported values are "iscsi" and "paravirtualized".
- instance
Id string - The OCID of the instance.
- volume
Id string The OCID of the volume.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- compartment
Id string - The OCID of the compartment.
- device string
- The device name. To retrieve a list of devices for a given instance, see ListInstanceDevices.
- display
Name string - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- encryption
In stringTransit Type - Refer the top-level definition of encryptionInTransitType. The default value is NONE.
- is
Agent booleanAuto Iscsi Login Enabled - Whether to enable Oracle Cloud Agent to perform the iSCSI login and logout commands after the volume attach or detach operations for non multipath-enabled iSCSI attachments.
- is
Pv booleanEncryption In Transit Enabled - Whether to enable in-transit encryption for the data volume's paravirtualized attachment. The default value is false.
- is
Read booleanOnly - Whether the attachment was created in read-only mode.
- boolean
- 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.
- use
Chap boolean - Whether to use CHAP authentication for the volume attachment. Defaults to false.
- attachment_
type str - The type of volume. The only supported values are "iscsi" and "paravirtualized".
- instance_
id str - The OCID of the instance.
- volume_
id str The OCID of the volume.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- compartment_
id str - The OCID of the compartment.
- device str
- The device name. To retrieve a list of devices for a given instance, see ListInstanceDevices.
- display_
name str - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- encryption_
in_ strtransit_ type - Refer the top-level definition of encryptionInTransitType. The default value is NONE.
- is_
agent_ boolauto_ iscsi_ login_ enabled - Whether to enable Oracle Cloud Agent to perform the iSCSI login and logout commands after the volume attach or detach operations for non multipath-enabled iSCSI attachments.
- is_
pv_ boolencryption_ in_ transit_ enabled - Whether to enable in-transit encryption for the data volume's paravirtualized attachment. The default value is false.
- is_
read_ boolonly - Whether the attachment was created in read-only mode.
- bool
- 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.
- use_
chap bool - Whether to use CHAP authentication for the volume attachment. Defaults to false.
- attachment
Type String - The type of volume. The only supported values are "iscsi" and "paravirtualized".
- instance
Id String - The OCID of the instance.
- volume
Id String The OCID of the volume.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- compartment
Id String - The OCID of the compartment.
- device String
- The device name. To retrieve a list of devices for a given instance, see ListInstanceDevices.
- display
Name String - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- encryption
In StringTransit Type - Refer the top-level definition of encryptionInTransitType. The default value is NONE.
- is
Agent BooleanAuto Iscsi Login Enabled - Whether to enable Oracle Cloud Agent to perform the iSCSI login and logout commands after the volume attach or detach operations for non multipath-enabled iSCSI attachments.
- is
Pv BooleanEncryption In Transit Enabled - Whether to enable in-transit encryption for the data volume's paravirtualized attachment. The default value is false.
- is
Read BooleanOnly - Whether the attachment was created in read-only mode.
- Boolean
- 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.
- use
Chap Boolean - Whether to use CHAP authentication for the volume attachment. Defaults to false.
Outputs
All input properties are implicitly available as output properties. Additionally, the VolumeAttachment resource produces the following output properties:
- Availability
Domain string - The availability domain of an instance. Example:
Uocm:PHX-AD-1 - Chap
Secret string - The Challenge-Handshake-Authentication-Protocol (CHAP) secret valid for the associated CHAP user name. (Also called the "CHAP password".)
- Chap
Username string - The volume's system-generated Challenge-Handshake-Authentication-Protocol (CHAP) user name. See RFC 1994 for more on CHAP. Example:
ocid1.volume.oc1.phx.<unique_ID> - Id string
- The provider-assigned unique ID for this managed resource.
- Ipv4 string
- The volume's iSCSI IP address. Example:
169.254.2.2 - Iqn string
- The target volume's iSCSI Qualified Name in the format defined by RFC 3720. Example:
iqn.2015-12.com.oracleiaas:40b7ee03-883f-46c6-a951-63d2841d2195 - Is
Multipath bool - Whether the Iscsi or Paravirtualized attachment is multipath or not, it is not applicable to NVMe attachment.
- Is
Volume boolCreated During Launch - Flag indicating if this volume was created for the customer as part of a simplified launch. Used to determine whether the volume requires deletion on instance termination.
- Iscsi
Login stringState - The iscsi login state of the volume attachment. For a Iscsi volume attachment, all iscsi sessions need to be all logged-in or logged-out to be in logged-in or logged-out state.
- Multipath
Devices List<VolumeAttachment Multipath Device> - A list of secondary multipath devices
- Port int
- The volume's iSCSI port, usually port 860 or 3260. Example:
3260 - State string
- The current state of the volume attachment.
- Time
Created string - The date and time the volume was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z
- Availability
Domain string - The availability domain of an instance. Example:
Uocm:PHX-AD-1 - Chap
Secret string - The Challenge-Handshake-Authentication-Protocol (CHAP) secret valid for the associated CHAP user name. (Also called the "CHAP password".)
- Chap
Username string - The volume's system-generated Challenge-Handshake-Authentication-Protocol (CHAP) user name. See RFC 1994 for more on CHAP. Example:
ocid1.volume.oc1.phx.<unique_ID> - Id string
- The provider-assigned unique ID for this managed resource.
- Ipv4 string
- The volume's iSCSI IP address. Example:
169.254.2.2 - Iqn string
- The target volume's iSCSI Qualified Name in the format defined by RFC 3720. Example:
iqn.2015-12.com.oracleiaas:40b7ee03-883f-46c6-a951-63d2841d2195 - Is
Multipath bool - Whether the Iscsi or Paravirtualized attachment is multipath or not, it is not applicable to NVMe attachment.
- Is
Volume boolCreated During Launch - Flag indicating if this volume was created for the customer as part of a simplified launch. Used to determine whether the volume requires deletion on instance termination.
- Iscsi
Login stringState - The iscsi login state of the volume attachment. For a Iscsi volume attachment, all iscsi sessions need to be all logged-in or logged-out to be in logged-in or logged-out state.
- Multipath
Devices []VolumeAttachment Multipath Device - A list of secondary multipath devices
- Port int
- The volume's iSCSI port, usually port 860 or 3260. Example:
3260 - State string
- The current state of the volume attachment.
- Time
Created string - The date and time the volume was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z
- availability
Domain String - The availability domain of an instance. Example:
Uocm:PHX-AD-1 - chap
Secret String - The Challenge-Handshake-Authentication-Protocol (CHAP) secret valid for the associated CHAP user name. (Also called the "CHAP password".)
- chap
Username String - The volume's system-generated Challenge-Handshake-Authentication-Protocol (CHAP) user name. See RFC 1994 for more on CHAP. Example:
ocid1.volume.oc1.phx.<unique_ID> - id String
- The provider-assigned unique ID for this managed resource.
- ipv4 String
- The volume's iSCSI IP address. Example:
169.254.2.2 - iqn String
- The target volume's iSCSI Qualified Name in the format defined by RFC 3720. Example:
iqn.2015-12.com.oracleiaas:40b7ee03-883f-46c6-a951-63d2841d2195 - is
Multipath Boolean - Whether the Iscsi or Paravirtualized attachment is multipath or not, it is not applicable to NVMe attachment.
- is
Volume BooleanCreated During Launch - Flag indicating if this volume was created for the customer as part of a simplified launch. Used to determine whether the volume requires deletion on instance termination.
- iscsi
Login StringState - The iscsi login state of the volume attachment. For a Iscsi volume attachment, all iscsi sessions need to be all logged-in or logged-out to be in logged-in or logged-out state.
- multipath
Devices List<VolumeAttachment Multipath Device> - A list of secondary multipath devices
- port Integer
- The volume's iSCSI port, usually port 860 or 3260. Example:
3260 - state String
- The current state of the volume attachment.
- time
Created String - The date and time the volume was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z
- availability
Domain string - The availability domain of an instance. Example:
Uocm:PHX-AD-1 - chap
Secret string - The Challenge-Handshake-Authentication-Protocol (CHAP) secret valid for the associated CHAP user name. (Also called the "CHAP password".)
- chap
Username string - The volume's system-generated Challenge-Handshake-Authentication-Protocol (CHAP) user name. See RFC 1994 for more on CHAP. Example:
ocid1.volume.oc1.phx.<unique_ID> - id string
- The provider-assigned unique ID for this managed resource.
- ipv4 string
- The volume's iSCSI IP address. Example:
169.254.2.2 - iqn string
- The target volume's iSCSI Qualified Name in the format defined by RFC 3720. Example:
iqn.2015-12.com.oracleiaas:40b7ee03-883f-46c6-a951-63d2841d2195 - is
Multipath boolean - Whether the Iscsi or Paravirtualized attachment is multipath or not, it is not applicable to NVMe attachment.
- is
Volume booleanCreated During Launch - Flag indicating if this volume was created for the customer as part of a simplified launch. Used to determine whether the volume requires deletion on instance termination.
- iscsi
Login stringState - The iscsi login state of the volume attachment. For a Iscsi volume attachment, all iscsi sessions need to be all logged-in or logged-out to be in logged-in or logged-out state.
- multipath
Devices VolumeAttachment Multipath Device[] - A list of secondary multipath devices
- port number
- The volume's iSCSI port, usually port 860 or 3260. Example:
3260 - state string
- The current state of the volume attachment.
- time
Created string - The date and time the volume was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z
- availability_
domain str - The availability domain of an instance. Example:
Uocm:PHX-AD-1 - chap_
secret str - The Challenge-Handshake-Authentication-Protocol (CHAP) secret valid for the associated CHAP user name. (Also called the "CHAP password".)
- chap_
username str - The volume's system-generated Challenge-Handshake-Authentication-Protocol (CHAP) user name. See RFC 1994 for more on CHAP. Example:
ocid1.volume.oc1.phx.<unique_ID> - id str
- The provider-assigned unique ID for this managed resource.
- ipv4 str
- The volume's iSCSI IP address. Example:
169.254.2.2 - iqn str
- The target volume's iSCSI Qualified Name in the format defined by RFC 3720. Example:
iqn.2015-12.com.oracleiaas:40b7ee03-883f-46c6-a951-63d2841d2195 - is_
multipath bool - Whether the Iscsi or Paravirtualized attachment is multipath or not, it is not applicable to NVMe attachment.
- is_
volume_ boolcreated_ during_ launch - Flag indicating if this volume was created for the customer as part of a simplified launch. Used to determine whether the volume requires deletion on instance termination.
- iscsi_
login_ strstate - The iscsi login state of the volume attachment. For a Iscsi volume attachment, all iscsi sessions need to be all logged-in or logged-out to be in logged-in or logged-out state.
- multipath_
devices Sequence[core.Volume Attachment Multipath Device] - A list of secondary multipath devices
- port int
- The volume's iSCSI port, usually port 860 or 3260. Example:
3260 - state str
- The current state of the volume attachment.
- time_
created str - The date and time the volume was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z
- availability
Domain String - The availability domain of an instance. Example:
Uocm:PHX-AD-1 - chap
Secret String - The Challenge-Handshake-Authentication-Protocol (CHAP) secret valid for the associated CHAP user name. (Also called the "CHAP password".)
- chap
Username String - The volume's system-generated Challenge-Handshake-Authentication-Protocol (CHAP) user name. See RFC 1994 for more on CHAP. Example:
ocid1.volume.oc1.phx.<unique_ID> - id String
- The provider-assigned unique ID for this managed resource.
- ipv4 String
- The volume's iSCSI IP address. Example:
169.254.2.2 - iqn String
- The target volume's iSCSI Qualified Name in the format defined by RFC 3720. Example:
iqn.2015-12.com.oracleiaas:40b7ee03-883f-46c6-a951-63d2841d2195 - is
Multipath Boolean - Whether the Iscsi or Paravirtualized attachment is multipath or not, it is not applicable to NVMe attachment.
- is
Volume BooleanCreated During Launch - Flag indicating if this volume was created for the customer as part of a simplified launch. Used to determine whether the volume requires deletion on instance termination.
- iscsi
Login StringState - The iscsi login state of the volume attachment. For a Iscsi volume attachment, all iscsi sessions need to be all logged-in or logged-out to be in logged-in or logged-out state.
- multipath
Devices List<Property Map> - A list of secondary multipath devices
- port Number
- The volume's iSCSI port, usually port 860 or 3260. Example:
3260 - state String
- The current state of the volume attachment.
- time
Created String - The date and time the volume was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z
Look up Existing VolumeAttachment Resource
Get an existing VolumeAttachment resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: VolumeAttachmentState, opts?: CustomResourceOptions): VolumeAttachment@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
attachment_type: Optional[str] = None,
availability_domain: Optional[str] = None,
chap_secret: Optional[str] = None,
chap_username: Optional[str] = None,
compartment_id: Optional[str] = None,
device: Optional[str] = None,
display_name: Optional[str] = None,
encryption_in_transit_type: Optional[str] = None,
instance_id: Optional[str] = None,
ipv4: Optional[str] = None,
iqn: Optional[str] = None,
is_agent_auto_iscsi_login_enabled: Optional[bool] = None,
is_multipath: Optional[bool] = None,
is_pv_encryption_in_transit_enabled: Optional[bool] = None,
is_read_only: Optional[bool] = None,
is_shareable: Optional[bool] = None,
is_volume_created_during_launch: Optional[bool] = None,
iscsi_login_state: Optional[str] = None,
multipath_devices: Optional[Sequence[_core.VolumeAttachmentMultipathDeviceArgs]] = None,
port: Optional[int] = None,
state: Optional[str] = None,
time_created: Optional[str] = None,
use_chap: Optional[bool] = None,
volume_id: Optional[str] = None) -> VolumeAttachmentfunc GetVolumeAttachment(ctx *Context, name string, id IDInput, state *VolumeAttachmentState, opts ...ResourceOption) (*VolumeAttachment, error)public static VolumeAttachment Get(string name, Input<string> id, VolumeAttachmentState? state, CustomResourceOptions? opts = null)public static VolumeAttachment get(String name, Output<String> id, VolumeAttachmentState state, CustomResourceOptions options)Resource lookup is not supported in YAML- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Attachment
Type string - The type of volume. The only supported values are "iscsi" and "paravirtualized".
- Availability
Domain string - The availability domain of an instance. Example:
Uocm:PHX-AD-1 - Chap
Secret string - The Challenge-Handshake-Authentication-Protocol (CHAP) secret valid for the associated CHAP user name. (Also called the "CHAP password".)
- Chap
Username string - The volume's system-generated Challenge-Handshake-Authentication-Protocol (CHAP) user name. See RFC 1994 for more on CHAP. Example:
ocid1.volume.oc1.phx.<unique_ID> - Compartment
Id string - The OCID of the compartment.
- Device string
- The device name. To retrieve a list of devices for a given instance, see ListInstanceDevices.
- Display
Name string - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- Encryption
In stringTransit Type - Refer the top-level definition of encryptionInTransitType. The default value is NONE.
- Instance
Id string - The OCID of the instance.
- Ipv4 string
- The volume's iSCSI IP address. Example:
169.254.2.2 - Iqn string
- The target volume's iSCSI Qualified Name in the format defined by RFC 3720. Example:
iqn.2015-12.com.oracleiaas:40b7ee03-883f-46c6-a951-63d2841d2195 - Is
Agent boolAuto Iscsi Login Enabled - Whether to enable Oracle Cloud Agent to perform the iSCSI login and logout commands after the volume attach or detach operations for non multipath-enabled iSCSI attachments.
- Is
Multipath bool - Whether the Iscsi or Paravirtualized attachment is multipath or not, it is not applicable to NVMe attachment.
- Is
Pv boolEncryption In Transit Enabled - Whether to enable in-transit encryption for the data volume's paravirtualized attachment. The default value is false.
- Is
Read boolOnly - Whether the attachment was created in read-only mode.
- bool
- 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.
- Is
Volume boolCreated During Launch - Flag indicating if this volume was created for the customer as part of a simplified launch. Used to determine whether the volume requires deletion on instance termination.
- Iscsi
Login stringState - The iscsi login state of the volume attachment. For a Iscsi volume attachment, all iscsi sessions need to be all logged-in or logged-out to be in logged-in or logged-out state.
- Multipath
Devices List<VolumeAttachment Multipath Device> - A list of secondary multipath devices
- Port int
- The volume's iSCSI port, usually port 860 or 3260. Example:
3260 - State string
- The current state of the volume attachment.
- Time
Created string - The date and time the volume was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z - Use
Chap bool - Whether to use CHAP authentication for the volume attachment. Defaults to false.
- Volume
Id string The OCID of the volume.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- Attachment
Type string - The type of volume. The only supported values are "iscsi" and "paravirtualized".
- Availability
Domain string - The availability domain of an instance. Example:
Uocm:PHX-AD-1 - Chap
Secret string - The Challenge-Handshake-Authentication-Protocol (CHAP) secret valid for the associated CHAP user name. (Also called the "CHAP password".)
- Chap
Username string - The volume's system-generated Challenge-Handshake-Authentication-Protocol (CHAP) user name. See RFC 1994 for more on CHAP. Example:
ocid1.volume.oc1.phx.<unique_ID> - Compartment
Id string - The OCID of the compartment.
- Device string
- The device name. To retrieve a list of devices for a given instance, see ListInstanceDevices.
- Display
Name string - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- Encryption
In stringTransit Type - Refer the top-level definition of encryptionInTransitType. The default value is NONE.
- Instance
Id string - The OCID of the instance.
- Ipv4 string
- The volume's iSCSI IP address. Example:
169.254.2.2 - Iqn string
- The target volume's iSCSI Qualified Name in the format defined by RFC 3720. Example:
iqn.2015-12.com.oracleiaas:40b7ee03-883f-46c6-a951-63d2841d2195 - Is
Agent boolAuto Iscsi Login Enabled - Whether to enable Oracle Cloud Agent to perform the iSCSI login and logout commands after the volume attach or detach operations for non multipath-enabled iSCSI attachments.
- Is
Multipath bool - Whether the Iscsi or Paravirtualized attachment is multipath or not, it is not applicable to NVMe attachment.
- Is
Pv boolEncryption In Transit Enabled - Whether to enable in-transit encryption for the data volume's paravirtualized attachment. The default value is false.
- Is
Read boolOnly - Whether the attachment was created in read-only mode.
- bool
- 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.
- Is
Volume boolCreated During Launch - Flag indicating if this volume was created for the customer as part of a simplified launch. Used to determine whether the volume requires deletion on instance termination.
- Iscsi
Login stringState - The iscsi login state of the volume attachment. For a Iscsi volume attachment, all iscsi sessions need to be all logged-in or logged-out to be in logged-in or logged-out state.
- Multipath
Devices []VolumeAttachment Multipath Device Args - A list of secondary multipath devices
- Port int
- The volume's iSCSI port, usually port 860 or 3260. Example:
3260 - State string
- The current state of the volume attachment.
- Time
Created string - The date and time the volume was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z - Use
Chap bool - Whether to use CHAP authentication for the volume attachment. Defaults to false.
- Volume
Id string The OCID of the volume.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- attachment
Type String - The type of volume. The only supported values are "iscsi" and "paravirtualized".
- availability
Domain String - The availability domain of an instance. Example:
Uocm:PHX-AD-1 - chap
Secret String - The Challenge-Handshake-Authentication-Protocol (CHAP) secret valid for the associated CHAP user name. (Also called the "CHAP password".)
- chap
Username String - The volume's system-generated Challenge-Handshake-Authentication-Protocol (CHAP) user name. See RFC 1994 for more on CHAP. Example:
ocid1.volume.oc1.phx.<unique_ID> - compartment
Id String - The OCID of the compartment.
- device String
- The device name. To retrieve a list of devices for a given instance, see ListInstanceDevices.
- display
Name String - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- encryption
In StringTransit Type - Refer the top-level definition of encryptionInTransitType. The default value is NONE.
- instance
Id String - The OCID of the instance.
- ipv4 String
- The volume's iSCSI IP address. Example:
169.254.2.2 - iqn String
- The target volume's iSCSI Qualified Name in the format defined by RFC 3720. Example:
iqn.2015-12.com.oracleiaas:40b7ee03-883f-46c6-a951-63d2841d2195 - is
Agent BooleanAuto Iscsi Login Enabled - Whether to enable Oracle Cloud Agent to perform the iSCSI login and logout commands after the volume attach or detach operations for non multipath-enabled iSCSI attachments.
- is
Multipath Boolean - Whether the Iscsi or Paravirtualized attachment is multipath or not, it is not applicable to NVMe attachment.
- is
Pv BooleanEncryption In Transit Enabled - Whether to enable in-transit encryption for the data volume's paravirtualized attachment. The default value is false.
- is
Read BooleanOnly - Whether the attachment was created in read-only mode.
- Boolean
- 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.
- is
Volume BooleanCreated During Launch - Flag indicating if this volume was created for the customer as part of a simplified launch. Used to determine whether the volume requires deletion on instance termination.
- iscsi
Login StringState - The iscsi login state of the volume attachment. For a Iscsi volume attachment, all iscsi sessions need to be all logged-in or logged-out to be in logged-in or logged-out state.
- multipath
Devices List<VolumeAttachment Multipath Device> - A list of secondary multipath devices
- port Integer
- The volume's iSCSI port, usually port 860 or 3260. Example:
3260 - state String
- The current state of the volume attachment.
- time
Created String - The date and time the volume was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z - use
Chap Boolean - Whether to use CHAP authentication for the volume attachment. Defaults to false.
- volume
Id String The OCID of the volume.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- attachment
Type string - The type of volume. The only supported values are "iscsi" and "paravirtualized".
- availability
Domain string - The availability domain of an instance. Example:
Uocm:PHX-AD-1 - chap
Secret string - The Challenge-Handshake-Authentication-Protocol (CHAP) secret valid for the associated CHAP user name. (Also called the "CHAP password".)
- chap
Username string - The volume's system-generated Challenge-Handshake-Authentication-Protocol (CHAP) user name. See RFC 1994 for more on CHAP. Example:
ocid1.volume.oc1.phx.<unique_ID> - compartment
Id string - The OCID of the compartment.
- device string
- The device name. To retrieve a list of devices for a given instance, see ListInstanceDevices.
- display
Name string - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- encryption
In stringTransit Type - Refer the top-level definition of encryptionInTransitType. The default value is NONE.
- instance
Id string - The OCID of the instance.
- ipv4 string
- The volume's iSCSI IP address. Example:
169.254.2.2 - iqn string
- The target volume's iSCSI Qualified Name in the format defined by RFC 3720. Example:
iqn.2015-12.com.oracleiaas:40b7ee03-883f-46c6-a951-63d2841d2195 - is
Agent booleanAuto Iscsi Login Enabled - Whether to enable Oracle Cloud Agent to perform the iSCSI login and logout commands after the volume attach or detach operations for non multipath-enabled iSCSI attachments.
- is
Multipath boolean - Whether the Iscsi or Paravirtualized attachment is multipath or not, it is not applicable to NVMe attachment.
- is
Pv booleanEncryption In Transit Enabled - Whether to enable in-transit encryption for the data volume's paravirtualized attachment. The default value is false.
- is
Read booleanOnly - Whether the attachment was created in read-only mode.
- boolean
- 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.
- is
Volume booleanCreated During Launch - Flag indicating if this volume was created for the customer as part of a simplified launch. Used to determine whether the volume requires deletion on instance termination.
- iscsi
Login stringState - The iscsi login state of the volume attachment. For a Iscsi volume attachment, all iscsi sessions need to be all logged-in or logged-out to be in logged-in or logged-out state.
- multipath
Devices VolumeAttachment Multipath Device[] - A list of secondary multipath devices
- port number
- The volume's iSCSI port, usually port 860 or 3260. Example:
3260 - state string
- The current state of the volume attachment.
- time
Created string - The date and time the volume was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z - use
Chap boolean - Whether to use CHAP authentication for the volume attachment. Defaults to false.
- volume
Id string The OCID of the volume.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- attachment_
type str - The type of volume. The only supported values are "iscsi" and "paravirtualized".
- availability_
domain str - The availability domain of an instance. Example:
Uocm:PHX-AD-1 - chap_
secret str - The Challenge-Handshake-Authentication-Protocol (CHAP) secret valid for the associated CHAP user name. (Also called the "CHAP password".)
- chap_
username str - The volume's system-generated Challenge-Handshake-Authentication-Protocol (CHAP) user name. See RFC 1994 for more on CHAP. Example:
ocid1.volume.oc1.phx.<unique_ID> - compartment_
id str - The OCID of the compartment.
- device str
- The device name. To retrieve a list of devices for a given instance, see ListInstanceDevices.
- display_
name str - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- encryption_
in_ strtransit_ type - Refer the top-level definition of encryptionInTransitType. The default value is NONE.
- instance_
id str - The OCID of the instance.
- ipv4 str
- The volume's iSCSI IP address. Example:
169.254.2.2 - iqn str
- The target volume's iSCSI Qualified Name in the format defined by RFC 3720. Example:
iqn.2015-12.com.oracleiaas:40b7ee03-883f-46c6-a951-63d2841d2195 - is_
agent_ boolauto_ iscsi_ login_ enabled - Whether to enable Oracle Cloud Agent to perform the iSCSI login and logout commands after the volume attach or detach operations for non multipath-enabled iSCSI attachments.
- is_
multipath bool - Whether the Iscsi or Paravirtualized attachment is multipath or not, it is not applicable to NVMe attachment.
- is_
pv_ boolencryption_ in_ transit_ enabled - Whether to enable in-transit encryption for the data volume's paravirtualized attachment. The default value is false.
- is_
read_ boolonly - Whether the attachment was created in read-only mode.
- bool
- 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.
- is_
volume_ boolcreated_ during_ launch - Flag indicating if this volume was created for the customer as part of a simplified launch. Used to determine whether the volume requires deletion on instance termination.
- iscsi_
login_ strstate - The iscsi login state of the volume attachment. For a Iscsi volume attachment, all iscsi sessions need to be all logged-in or logged-out to be in logged-in or logged-out state.
- multipath_
devices Sequence[core.Volume Attachment Multipath Device Args] - A list of secondary multipath devices
- port int
- The volume's iSCSI port, usually port 860 or 3260. Example:
3260 - state str
- The current state of the volume attachment.
- time_
created str - The date and time the volume was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z - use_
chap bool - Whether to use CHAP authentication for the volume attachment. Defaults to false.
- volume_
id str The OCID of the volume.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
- attachment
Type String - The type of volume. The only supported values are "iscsi" and "paravirtualized".
- availability
Domain String - The availability domain of an instance. Example:
Uocm:PHX-AD-1 - chap
Secret String - The Challenge-Handshake-Authentication-Protocol (CHAP) secret valid for the associated CHAP user name. (Also called the "CHAP password".)
- chap
Username String - The volume's system-generated Challenge-Handshake-Authentication-Protocol (CHAP) user name. See RFC 1994 for more on CHAP. Example:
ocid1.volume.oc1.phx.<unique_ID> - compartment
Id String - The OCID of the compartment.
- device String
- The device name. To retrieve a list of devices for a given instance, see ListInstanceDevices.
- display
Name String - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- encryption
In StringTransit Type - Refer the top-level definition of encryptionInTransitType. The default value is NONE.
- instance
Id String - The OCID of the instance.
- ipv4 String
- The volume's iSCSI IP address. Example:
169.254.2.2 - iqn String
- The target volume's iSCSI Qualified Name in the format defined by RFC 3720. Example:
iqn.2015-12.com.oracleiaas:40b7ee03-883f-46c6-a951-63d2841d2195 - is
Agent BooleanAuto Iscsi Login Enabled - Whether to enable Oracle Cloud Agent to perform the iSCSI login and logout commands after the volume attach or detach operations for non multipath-enabled iSCSI attachments.
- is
Multipath Boolean - Whether the Iscsi or Paravirtualized attachment is multipath or not, it is not applicable to NVMe attachment.
- is
Pv BooleanEncryption In Transit Enabled - Whether to enable in-transit encryption for the data volume's paravirtualized attachment. The default value is false.
- is
Read BooleanOnly - Whether the attachment was created in read-only mode.
- Boolean
- 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.
- is
Volume BooleanCreated During Launch - Flag indicating if this volume was created for the customer as part of a simplified launch. Used to determine whether the volume requires deletion on instance termination.
- iscsi
Login StringState - The iscsi login state of the volume attachment. For a Iscsi volume attachment, all iscsi sessions need to be all logged-in or logged-out to be in logged-in or logged-out state.
- multipath
Devices List<Property Map> - A list of secondary multipath devices
- port Number
- The volume's iSCSI port, usually port 860 or 3260. Example:
3260 - state String
- The current state of the volume attachment.
- time
Created String - The date and time the volume was created, in the format defined by RFC3339. Example:
2016-08-25T21:10:29.600Z - use
Chap Boolean - Whether to use CHAP authentication for the volume attachment. Defaults to false.
- volume
Id String The OCID of the volume.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
Supporting Types
VolumeAttachmentMultipathDevice, VolumeAttachmentMultipathDeviceArgs
Import
VolumeAttachments can be imported using the id, e.g.
$ pulumi import oci:Core/volumeAttachment:VolumeAttachment test_volume_attachment "id"
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
ociTerraform Provider.