Table: oci_functions_application - Query OCI Functions Applications using SQL
Oracle Cloud Infrastructure Functions is a fully managed, multi-tenant, highly scalable, on-demand, Functions-as-a-Service platform. It allows developers to write and deploy code with functions that are triggered by events or direct invocations. Applications in OCI Functions represent a logical grouping of functions, and the oci_functions_application
table can be used to query these Applications.
Table Usage Guide
The oci_functions_application
table provides insights into Applications within the Oracle Cloud Infrastructure Functions service. As a developer or DevOps engineer, explore Application-specific details through this table, including the configuration and state of each Application. Utilize it to uncover information about the Applications, such as their associated functions, the network configuration, and the compartment they belong to.
Examples
Basic info
Discover the status and identifiers of your Oracle Cloud Infrastructure's functions applications. This allows for a quick overview and understanding of your application's lifecycle state and associated subnet IDs.
select display_name, id, lifecycle_state as state, lifecycle_state, subnet_idsfrom oci_functions_application;
select display_name, id, lifecycle_state as state, lifecycle_state, subnet_idsfrom oci_functions_application;
List applications not in the active state
Determine the areas in which applications are not currently active. This can help in identifying applications that may need attention or troubleshooting, thereby ensuring smooth operations.
select display_name, id, lifecycle_state as statefrom oci_functions_applicationwhere lifecycle_state <> 'ACTIVE';
select display_name, id, lifecycle_state as statefrom oci_functions_applicationwhere lifecycle_state <> 'ACTIVE';
Get configuration details for each application
Analyze the settings to understand each application's configuration within Oracle Cloud Infrastructure's Functions service. This allows for a comprehensive review of application settings, aiding in optimization and troubleshooting efforts.
select display_name, id, configfrom oci_functions_application;
select display_name, id, configfrom oci_functions_application;
Schema for oci_functions_application
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. |
config | jsonb | Application configuration for functions in this application. | |
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. | |
display_name | text | = | The display name of the application. |
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 application. |
lifecycle_state | text | = | The current state of the application. |
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. | |
subnet_ids | jsonb | The OCIDs of the subnets in which to run functions in the application. | |
syslog_url | text | A syslog URL to which to send all function logs. Supports tcp, udp, and tcp+tls. | |
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 time the application was created. | |
time_updated | timestamp with time zone | The time the application was updated. | |
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_functions_application