oci.Core.getVolumeAttachments
Explore with Pulumi AI
This data source provides the list of Volume Attachments in Oracle Cloud Infrastructure Core service.
Lists the volume attachments in the specified compartment. You can filter the list by specifying an instance OCID, volume OCID, or both.
Currently, the only supported volume attachment type are IScsiVolumeAttachment and ParavirtualizedVolumeAttachment.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testVolumeAttachments = oci.Core.getVolumeAttachments({
compartmentId: compartmentId,
availabilityDomain: volumeAttachmentAvailabilityDomain,
instanceId: testInstance.id,
volumeId: testVolume.id,
});
import pulumi
import pulumi_oci as oci
test_volume_attachments = oci.Core.get_volume_attachments(compartment_id=compartment_id,
availability_domain=volume_attachment_availability_domain,
instance_id=test_instance["id"],
volume_id=test_volume["id"])
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.GetVolumeAttachments(ctx, &core.GetVolumeAttachmentsArgs{
CompartmentId: compartmentId,
AvailabilityDomain: pulumi.StringRef(volumeAttachmentAvailabilityDomain),
InstanceId: pulumi.StringRef(testInstance.Id),
VolumeId: pulumi.StringRef(testVolume.Id),
}, nil)
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 testVolumeAttachments = Oci.Core.GetVolumeAttachments.Invoke(new()
{
CompartmentId = compartmentId,
AvailabilityDomain = volumeAttachmentAvailabilityDomain,
InstanceId = testInstance.Id,
VolumeId = testVolume.Id,
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.oci.Core.CoreFunctions;
import com.pulumi.oci.Core.inputs.GetVolumeAttachmentsArgs;
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) {
final var testVolumeAttachments = CoreFunctions.getVolumeAttachments(GetVolumeAttachmentsArgs.builder()
.compartmentId(compartmentId)
.availabilityDomain(volumeAttachmentAvailabilityDomain)
.instanceId(testInstance.id())
.volumeId(testVolume.id())
.build());
}
}
variables:
testVolumeAttachments:
fn::invoke:
Function: oci:Core:getVolumeAttachments
Arguments:
compartmentId: ${compartmentId}
availabilityDomain: ${volumeAttachmentAvailabilityDomain}
instanceId: ${testInstance.id}
volumeId: ${testVolume.id}
Using getVolumeAttachments
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getVolumeAttachments(args: GetVolumeAttachmentsArgs, opts?: InvokeOptions): Promise<GetVolumeAttachmentsResult>
function getVolumeAttachmentsOutput(args: GetVolumeAttachmentsOutputArgs, opts?: InvokeOptions): Output<GetVolumeAttachmentsResult>
def get_volume_attachments(availability_domain: Optional[str] = None,
compartment_id: Optional[str] = None,
filters: Optional[Sequence[_core.GetVolumeAttachmentsFilter]] = None,
instance_id: Optional[str] = None,
volume_id: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetVolumeAttachmentsResult
def get_volume_attachments_output(availability_domain: Optional[pulumi.Input[str]] = None,
compartment_id: Optional[pulumi.Input[str]] = None,
filters: Optional[pulumi.Input[Sequence[pulumi.Input[_core.GetVolumeAttachmentsFilterArgs]]]] = None,
instance_id: Optional[pulumi.Input[str]] = None,
volume_id: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetVolumeAttachmentsResult]
func GetVolumeAttachments(ctx *Context, args *GetVolumeAttachmentsArgs, opts ...InvokeOption) (*GetVolumeAttachmentsResult, error)
func GetVolumeAttachmentsOutput(ctx *Context, args *GetVolumeAttachmentsOutputArgs, opts ...InvokeOption) GetVolumeAttachmentsResultOutput
> Note: This function is named GetVolumeAttachments
in the Go SDK.
public static class GetVolumeAttachments
{
public static Task<GetVolumeAttachmentsResult> InvokeAsync(GetVolumeAttachmentsArgs args, InvokeOptions? opts = null)
public static Output<GetVolumeAttachmentsResult> Invoke(GetVolumeAttachmentsInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetVolumeAttachmentsResult> getVolumeAttachments(GetVolumeAttachmentsArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: oci:Core/getVolumeAttachments:getVolumeAttachments
arguments:
# arguments dictionary
The following arguments are supported:
- Compartment
Id string - The OCID of the compartment.
- Availability
Domain string - The name of the availability domain. Example:
Uocm:PHX-AD-1
- Filters
List<Get
Volume Attachments Filter> - Instance
Id string - The OCID of the instance.
- Volume
Id string - The OCID of the volume.
- Compartment
Id string - The OCID of the compartment.
- Availability
Domain string - The name of the availability domain. Example:
Uocm:PHX-AD-1
- Filters
[]Get
Volume Attachments Filter - Instance
Id string - The OCID of the instance.
- Volume
Id string - The OCID of the volume.
- compartment
Id String - The OCID of the compartment.
- availability
Domain String - The name of the availability domain. Example:
Uocm:PHX-AD-1
- filters
List<Get
Volume Attachments Filter> - instance
Id String - The OCID of the instance.
- volume
Id String - The OCID of the volume.
- compartment
Id string - The OCID of the compartment.
- availability
Domain string - The name of the availability domain. Example:
Uocm:PHX-AD-1
- filters
Get
Volume Attachments Filter[] - instance
Id string - The OCID of the instance.
- volume
Id string - The OCID of the volume.
- compartment_
id str - The OCID of the compartment.
- availability_
domain str - The name of the availability domain. Example:
Uocm:PHX-AD-1
- filters
Sequence[core.
Get Volume Attachments Filter] - instance_
id str - The OCID of the instance.
- volume_
id str - The OCID of the volume.
- compartment
Id String - The OCID of the compartment.
- availability
Domain String - The name of the availability domain. Example:
Uocm:PHX-AD-1
- filters List<Property Map>
- instance
Id String - The OCID of the instance.
- volume
Id String - The OCID of the volume.
getVolumeAttachments Result
The following output properties are available:
- Compartment
Id string - The OCID of the compartment.
- Id string
- The provider-assigned unique ID for this managed resource.
- Volume
Attachments List<GetVolume Attachments Volume Attachment> - The list of volume_attachments.
- Availability
Domain string - The availability domain of an instance. Example:
Uocm:PHX-AD-1
- Filters
List<Get
Volume Attachments Filter> - Instance
Id string - The OCID of the instance the volume is attached to.
- Volume
Id string - The OCID of the volume.
- Compartment
Id string - The OCID of the compartment.
- Id string
- The provider-assigned unique ID for this managed resource.
- Volume
Attachments []GetVolume Attachments Volume Attachment - The list of volume_attachments.
- Availability
Domain string - The availability domain of an instance. Example:
Uocm:PHX-AD-1
- Filters
[]Get
Volume Attachments Filter - Instance
Id string - The OCID of the instance the volume is attached to.
- Volume
Id string - The OCID of the volume.
- compartment
Id String - The OCID of the compartment.
- id String
- The provider-assigned unique ID for this managed resource.
- volume
Attachments List<GetVolume Attachments Volume Attachment> - The list of volume_attachments.
- availability
Domain String - The availability domain of an instance. Example:
Uocm:PHX-AD-1
- filters
List<Get
Volume Attachments Filter> - instance
Id String - The OCID of the instance the volume is attached to.
- volume
Id String - The OCID of the volume.
- compartment
Id string - The OCID of the compartment.
- id string
- The provider-assigned unique ID for this managed resource.
- volume
Attachments GetVolume Attachments Volume Attachment[] - The list of volume_attachments.
- availability
Domain string - The availability domain of an instance. Example:
Uocm:PHX-AD-1
- filters
Get
Volume Attachments Filter[] - instance
Id string - The OCID of the instance the volume is attached to.
- volume
Id string - The OCID of the volume.
- compartment_
id str - The OCID of the compartment.
- id str
- The provider-assigned unique ID for this managed resource.
- volume_
attachments Sequence[core.Get Volume Attachments Volume Attachment] - The list of volume_attachments.
- availability_
domain str - The availability domain of an instance. Example:
Uocm:PHX-AD-1
- filters
Sequence[core.
Get Volume Attachments Filter] - instance_
id str - The OCID of the instance the volume is attached to.
- volume_
id str - The OCID of the volume.
- compartment
Id String - The OCID of the compartment.
- id String
- The provider-assigned unique ID for this managed resource.
- volume
Attachments List<Property Map> - The list of volume_attachments.
- availability
Domain String - The availability domain of an instance. Example:
Uocm:PHX-AD-1
- filters List<Property Map>
- instance
Id String - The OCID of the instance the volume is attached to.
- volume
Id String - The OCID of the volume.
Supporting Types
GetVolumeAttachmentsFilter
GetVolumeAttachmentsVolumeAttachment
- Attachment
Type string - The type of volume attachment.
- Availability
Domain string - The name of the availability domain. 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.
- 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.
- Id string
- The OCID of the volume attachment.
- 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 Oracle Cloud Agent is enabled 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 in-transit encryption for the data volume's paravirtualized attachment is enabled or not.
- Is
Read boolOnly - Whether the attachment was created in read-only mode.
- bool
- 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<GetVolume Attachments 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 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 - Volume
Id string - The OCID of the volume.
- Attachment
Type string - The type of volume attachment.
- Availability
Domain string - The name of the availability domain. 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.
- 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.
- Id string
- The OCID of the volume attachment.
- 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 Oracle Cloud Agent is enabled 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 in-transit encryption for the data volume's paravirtualized attachment is enabled or not.
- Is
Read boolOnly - Whether the attachment was created in read-only mode.
- bool
- 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 []GetVolume Attachments 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 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 - Volume
Id string - The OCID of the volume.
- attachment
Type String - The type of volume attachment.
- availability
Domain String - The name of the availability domain. 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.
- 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.
- id String
- The OCID of the volume attachment.
- 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 Oracle Cloud Agent is enabled 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 in-transit encryption for the data volume's paravirtualized attachment is enabled or not.
- is
Read BooleanOnly - Whether the attachment was created in read-only mode.
- Boolean
- 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<GetVolume Attachments Volume Attachment 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 - volume
Id String - The OCID of the volume.
- attachment
Type string - The type of volume attachment.
- availability
Domain string - The name of the availability domain. 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.
- 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.
- id string
- The OCID of the volume attachment.
- 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 Oracle Cloud Agent is enabled 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 in-transit encryption for the data volume's paravirtualized attachment is enabled or not.
- is
Read booleanOnly - Whether the attachment was created in read-only mode.
- boolean
- 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 GetVolume Attachments Volume Attachment 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 - volume
Id string - The OCID of the volume.
- attachment_
type str - The type of volume attachment.
- availability_
domain str - The name of the availability domain. 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.
- 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.
- id str
- The OCID of the volume attachment.
- 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 Oracle Cloud Agent is enabled 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 in-transit encryption for the data volume's paravirtualized attachment is enabled or not.
- is_
read_ boolonly - Whether the attachment was created in read-only mode.
- bool
- 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.Get Volume Attachments 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
- use_
chap bool - volume_
id str - The OCID of the volume.
- attachment
Type String - The type of volume attachment.
- availability
Domain String - The name of the availability domain. 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.
- 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.
- id String
- The OCID of the volume attachment.
- 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 Oracle Cloud Agent is enabled 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 in-transit encryption for the data volume's paravirtualized attachment is enabled or not.
- is
Read BooleanOnly - Whether the attachment was created in read-only mode.
- Boolean
- 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 - volume
Id String - The OCID of the volume.
GetVolumeAttachmentsVolumeAttachmentMultipathDevice
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
oci
Terraform Provider.