Table: env0_project - Query Env0 Projects using SQL
Env0 is a platform that enables Infrastructure as Code (IaC) as part of the software development lifecycle. It allows developers to manage and govern their cloud resources, providing an automated, collaborative, and programmatically controlled cloud management solution. Env0 supports a range of IaC frameworks, including Terraform, and offers features such as cost estimation and policy enforcement.
Table Usage Guide
The env0_project
table provides insights into projects within the Env0 platform. As a DevOps engineer, you can explore project-specific details through this table, including project settings, associated users, and environments. Utilize it to uncover information about projects, such as those with specific environment settings, the users associated with each project, and the status of each project.
Examples
Basic info
Explore which projects have been archived within your organization. This allows for a quick overview of project status and can help identify inactive projects for potential cleanup or resource reallocation.
select name, id, created_by, created_by_user, organization_id, is_archivedfrom env0_project;
select name, id, created_by, created_by_user, organization_id, is_archivedfrom env0_project;
List project created in the last 30 days
Discover projects that have been initiated within the past month. This allows you to stay updated with new developments and assess the latest projects in your organization.
select name, id, created_by, created_by_user, organization_id, is_archivedfrom env0_projectwhere created_at >= now() - interval '30' day;
select name, id, created_by, created_by_user, organization_id, is_archivedfrom env0_projectwhere created_at >= datetime('now', '-30 day');
List projects that have not been updated in the last 30 days
Explore projects that have been inactive for the past 30 days. This can be particularly useful for identifying and managing outdated or neglected projects, thereby improving overall operational efficiency.
select name, id, created_by, created_by_user, role, organization_id, is_archivedfrom env0_projectwhere updated_at <= now() - interval '30' day;
select name, id, created_by, created_by_user, role, organization_id, is_archivedfrom env0_projectwhere updated_at <= datetime('now', '-30 day');
List unarchived projects
Discover the segments that are currently active in your project portfolio by identifying projects that are not archived. This aids in focusing resources and attention on ongoing initiatives, ensuring efficient project management.
select name, id, created_by, created_by_user, role, organization_id, is_archivedfrom env0_projectwhere is_archived is false;
select name, id, created_by, created_by_user, role, organization_id, is_archivedfrom env0_projectwhere is_archived = 0;
List projects that do not implement continuous deployment
Determine the areas in which continuous deployment is not implemented for projects. This analysis can help in identifying potential gaps in the development process and drive improvements in the deployment strategy.
select created_by, created_by_user, id, is_archived, name, organization_id rolefrom env0_projectwhere project_policy ->> 'continuousDeploymentDefault' = 'false';
select created_by, created_by_user, id, is_archived, name, organization_id, rolefrom env0_projectwhere json_extract(project_policy, '$.continuousDeploymentDefault') = 'false';
Get all project policy settings of specific project
Identify and understand the policy settings for a specific project, including the maximum number of environments and default approval requirements. This can be useful for project managers to monitor and control project settings, ensuring efficient resource utilization and adherence to project guidelines.
select name, organization_id, project_policy ->> 'numberOfEnvironmentsTotal' as max_no_of_environments, project_policy ->> 'requiresApprovalDefault' as requires_approval_default, project_policy ->> 'numberOfEnvironments' as no_of_environment, project_policy ->> 'continuousDeploymentDefault' as continuous_deployment_default, project_policy ->> 'maxTtl' as max_ttl, project_policy ->> 'defaultTtl' as default_ttlfrom env0_projectwhere id = '4a639364-1234-4eee-5678-ad38e1c1ccee';
select name, organization_id, json_extract(project_policy, '$.numberOfEnvironmentsTotal') as max_no_of_environments, json_extract(project_policy, '$.requiresApprovalDefault') as requires_approval_default, json_extract(project_policy, '$.numberOfEnvironments') as no_of_environment, json_extract(project_policy, '$.continuousDeploymentDefault') as continuous_deployment_default, json_extract(project_policy, '$.maxTtl') as max_ttl, json_extract(project_policy, '$.defaultTtl') as default_ttlfrom env0_projectwhere id = '4a639364-1234-4eee-5678-ad38e1c1ccee';
Schema for env0_project
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
created_at | timestamp with time zone | The date and time when project was created | |
created_by | text | Name of the authentication type used for creation of project. | |
created_by_user | text | Details of the user who created the project. | |
description | text | Description associated with the project. | |
id | text | = | Unique identifier of the project. |
is_archived | boolean | Whether or not the project is archived. | |
name | text | Name of the project. | |
organization_id | text | =, !=, ~~, ~~*, !~~, !~~* | The organization ID in which the project is located. |
parent_project_id | text | Parent project id of the project. | |
project_policy | jsonb | Associated project policy with the project | |
role | text | The role of the person who created the project. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
title | text | Title of the resource. | |
updated_at | timestamp with time zone | The date and time when project was updated |
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)" -- env0
You can pass the configuration to the command with the --config
argument:
steampipe_export_env0 --config '<your_config>' env0_project