Table: oci_mysql_configuration_custom - Query OCI MySQL Custom Configurations using SQL
The Oracle Cloud Infrastructure (OCI) MySQL Database Service is a fully managed database service that enables organizations to deploy cloud-native applications using the world's most popular open source database. It is developed, managed, and maintained by the same team that develops MySQL, ensuring up-to-date features, compatibility, and enhancements. A custom configuration in OCI MySQL Database Service allows users to customize various MySQL system variables to suit their specific requirements.
Table Usage Guide
The oci_mysql_configuration_custom
table provides insights into custom configurations within OCI MySQL Database Service. As a database administrator or developer, explore configuration-specific details through this table, including the configuration's ID, name, description, shape name, and various MySQL variables. Utilize it to uncover information about specific custom configurations, such as their variable settings, the MySQL version they're compatible with, and their associated compartment ID.
Examples
Basic info
Uncover the details of custom MySQL configurations in your Oracle Cloud Infrastructure, including their display names, IDs, descriptions, lifecycle states, and creation times. This can help you manage and monitor your custom configurations more effectively.
select display_name, id, description, lifecycle_state as state, time_createdfrom oci_mysql_configuration_custom;
select display_name, id, description, lifecycle_state as state, time_createdfrom oci_mysql_configuration_custom;
List deleted configurations
Explore which custom MySQL configurations have been deleted in your Oracle Cloud Infrastructure. This is useful for tracking changes and maintaining the security and efficiency of your database systems.
select display_name, id, description, lifecycle_state as state, time_createdfrom oci_mysql_configuration_customwhere lifecycle_state = 'DELETED';
select display_name, id, description, lifecycle_state as state, time_createdfrom oci_mysql_configuration_customwhere lifecycle_state = 'DELETED';
Schema for oci_mysql_configuration_custom
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
compartment_id | text | = | The OCID of the compartment in Tenant in which the resource is located. |
defined_tags | jsonb | Defined tags for resource. Defined tags are set up in your tenancy by an administrator. Only users granted permission to work with the defined tags can apply them to resources. | |
description | text | User-provided data about the configuration. | |
display_name | text | = | The display name of the configuration. |
freeform_tags | jsonb | Free-form tags for resource. This tags can be applied by any user with permissions on the resource. | |
id | text | = | The OCID of the configuration. |
lifecycle_state | text | = | The current state of the configuration. |
parent_configuration_id | text | The OCID of the configuration from which this configuration is derived. | |
region | text | The OCI region in which the resource is located. | |
shape_name | text | = | The name of the associated shape. |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
tags | jsonb | A map of tags for the resource. | |
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 configuration was created. | |
time_updated | timestamp with time zone | The date and time the configuration was last updated. | |
title | text | Title of the resource. | |
type | text | The configuration type, DEFAULT or CUSTOM. | |
variables | text | User controllable service variables of the configuration. |
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_mysql_configuration_custom