Table: oci_core_boot_volume_attachment - Query OCI Core Boot Volume Attachments using SQL
A Boot Volume Attachment in OCI (Oracle Cloud Infrastructure) is a relationship between a boot volume and an instance, which defines the boot volume from which an instance boots. The boot volume contains the image used to boot the instance, including the operating system and any installed software. The attachment is a critical component for an instance's functionality.
Table Usage Guide
The oci_core_boot_volume_attachment
table provides insights into boot volume attachments within OCI Core services. As a Cloud Administrator, explore attachment-specific details through this table, including the state of the attachment, the type of instance attached, and the availability domain. Utilize it to uncover information about boot volume attachments, such as the boot volume's lifecycle state, the time it was created, and the specific OCID (Oracle Cloud Identifier) for the attachment.
Examples
Basic info
Discover the segments that are in various stages of their lifecycle and when they were created. This query helps to manage and track resources effectively by providing insights into their current state and creation time.
select id, display_name, lifecycle_state, time_createdfrom oci_core_boot_volume_attachment;
select id, display_name, lifecycle_state, time_createdfrom oci_core_boot_volume_attachment;
List volume attachments witch are not attached
Analyze the settings to understand the status of volume attachments that are not currently connected. This could be beneficial for managing storage resources and ensuring efficient utilization.
select id, display_name, lifecycle_state, time_createdfrom oci_core_boot_volume_attachmentwhere lifecycle_state <> 'ATTACHED';
select id, display_name, lifecycle_state, time_createdfrom oci_core_boot_volume_attachmentwhere lifecycle_state <> 'ATTACHED';
Query examples
Schema for oci_core_boot_volume_attachment
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
availability_domain | text | = | The availability domain of an instance. |
boot_volume_id | text | = | The OCID of the boot volume. |
compartment_id | text | = | The OCID of the compartment in Tenant in which the resource is located. |
display_name | text | A user-friendly name. Does not have to be unique, and it cannot be changed. | |
encryption_in_transit_type | text | The type of the encryption in transit for the boot volume. | |
id | text | = | The OCID of the boot volume attachment. |
instance_id | text | = | The OCID of the instance the boot volume is attached to. |
is_pv_encryption_in_transit_enabled | boolean | Whether in-transit encryption for the boot volume's paravirtualized attachment is enabled or not. | |
lifecycle_state | text | The current state of the boot volume attachment. | |
region | text | The OCI region in which the resource is located. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
tenant_id | text | =, !=, ~~, ~~*, !~~, !~~* | The OCID of the Tenant in which the resource is located. |
tenant_name | text | The name of the Tenant in which the resource is located. | |
time_created | timestamp with time zone | The date and time the boot volume was created. | |
title | text | Title of the resource. |
Export
This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.
You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh
script:
/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- oci
You can pass the configuration to the command with the --config
argument:
steampipe_export_oci --config '<your_config>' oci_core_boot_volume_attachment