Table: oci_devops_project - Query OCI DevOps Projects using SQL
A DevOps Project in Oracle Cloud Infrastructure (OCI) is a managed environment that provides a set of resources for developing, testing, and delivering applications in the cloud. It offers a unified interface for managing both infrastructure as code and application code, helping developers and operations teams work together more effectively. DevOps Projects in OCI enable continuous integration and delivery, infrastructure automation, and other DevOps practices.
Table Usage Guide
The oci_devops_project
table provides insights into DevOps Projects within Oracle Cloud Infrastructure. As a DevOps engineer, you can explore project-specific details through this table, including project details, associated resources, and other metadata. Utilize it to uncover information about projects, such as those with specific configurations, the relationships between resources within a project, and the status of different elements of the project.
Examples
Basic info
Explore the status and timing of your DevOps projects. This query allows you to monitor project progress and updates, providing insight into the lifecycle and timelines of your projects.
select name, id, description, namespace, lifecycle_state, time_created, time_updatedfrom oci_devops_project;
select name, id, description, namespace, lifecycle_state, time_created, time_updatedfrom oci_devops_project;
Join DevOps Projects with Notification Topics
Explore the connection between DevOps projects and their corresponding notification topics. This can be crucial in managing project notifications and understanding the overall project configuration.
select project.name, project.id, project.notification_topic_id, topic.name notification_topic_name, project.namespace, project.descriptionfrom oci_devops_project project left join oci_ons_notification_topic topic on project.notification_topic_id = topic.topic_id;
select project.name, project.id, project.notification_topic_id, topic.name as notification_topic_name, project.namespace, project.descriptionfrom oci_devops_project as project left join oci_ons_notification_topic as topic on project.notification_topic_id = topic.topic_id;
List projects that are not active
Discover the segments that consist of inactive projects within your organisation. This can be useful to identify and manage projects that are no longer in use, thereby optimizing resources and improving operational efficiency.
select name, id, lifecycle_state, time_created, namespacefrom oci_devops_projectwhere lifecycle_state <> 'ACTIVE';
select name, id, lifecycle_state, time_created, namespacefrom oci_devops_projectwhere lifecycle_state <> 'ACTIVE';
List projects that are created in the last 30 days
Explore which projects have been initiated in the recent 30 days. This is useful for tracking recent development activities and ensuring necessary follow-ups.
select name, id, time_created, namespacefrom oci_devops_projectwhere time_created >= now() - interval '30' day;
select name, id, time_created, namespacefrom oci_devops_projectwhere time_created >= datetime('now', '-30 day');
Schema for oci_devops_project
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 | The description of the project. | |
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 project. |
lifecycle_details | text | A message describing the current state in more detail. For example, can be used to provide actionable information for a resource in Failed state. | |
lifecycle_state | text | The current state of the project. | |
name | text | = | The name of the project. |
namespace | text | Namespace associated with the project. | |
notification_topic_id | text | The topic ID for the topic where project notifications will be published to. | |
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. | |
system_tags | jsonb | System tags for resource. System tags can be viewed by users, but can only be created by the system. | |
tags | jsonb | A map of tags for the resource. | |
tenant_id | text | =, !=, ~~, ~~*, !~~, !~~* | The OCID of the Tenant in which the resource is located. |
time_created | timestamp with time zone | The date and time the project was created. | |
time_updated | timestamp with time zone | The date and time the project was last modified. | |
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_devops_project