The CloudQuery env zero (env0) plugin extracts Infrastructure-as-Code platform data - organizations, projects, environments, deployments, modules, templates, cloud accounts, and more - and loads it into any supported CloudQuery destination (e.g. PostgreSQL, BigQuery, Snowflake, and more).
Publisher
cloudquery
Latest version
v3.0.0
Type
Source
Platforms
Date Published
Loading plugin documentation
CloudQuery's use of cookies
We use tracking cookies to understand how you use the product and help us improve it. Your consent is required before we can enable these cookies. You can opt out via the link in the footer.
spec:
api_key_id: "${ENVZERO_API_KEY_ID}"
api_key_secret: "${ENVZERO_API_KEY_SECRET}"
kind: source
spec:
name: "envzero"
path: "cloudquery/envzero"
registry: "cloudquery"
version: "v3.0.0"
tables: ["*"]
destinations: ["postgresql"]
spec:
api_key_id: "${ENVZERO_API_KEY_ID}"
api_key_secret: "${ENVZERO_API_KEY_SECRET}"
table_options: spec:
api_key_id: "${ENVZERO_API_KEY_ID}"
api_key_secret: "${ENVZERO_API_KEY_SECRET}"
table_options:
envzero_deployments:
max_per_environment: 0 # 0 = full history; omit for the default of 100
kind: source
spec:
name: "envzero"
path: "cloudquery/envzero"
registry: "cloudquery"
version: "v3.0.0"
tables: ["*"]
destinations: ["postgresql"]
backend_options:
table_name: "cq_state_envzero"
connection: "@@plugins.postgresql.connection"
spec:
api_key_id: "${ENVZERO_API_KEY_ID}"
api_key_secret: "${ENVZERO_API_KEY_SECRET}"
table_options:
envzero_deployments:
deployment_types: ["deploy", "destroy"]
api_key_id (string) (required)api_key_secret (string) (required)host (string, optional, default: https://api.env0.com)organization_id (string, optional)project_ids ([]string, optional)concurrency (integer, optional, default: 500)scheduler (string, optional, default: dfs)dfs (depth-first search), round-robin, shuffle and shuffle-queue.table_options (object, optional)envzero_deployments defaults to the 100 most-recent deployments per environment (max_per_environment: 0 for full history); the cap applies to every full sync, so configure backend_options for incremental, uncapped syncs. See the envzero_deployments table docs for all options.SELECT
e.organization_id,
e.project_id,
e.name,
e.status,
e.workspace_name,
e.created_at,
e.updated_at
FROM envzero_environments e
WHERE e.is_archived IS FALSE
ORDER BY e.organization_id, e.updated_at DESC;
SELECT DISTINCT ON (d.environment_id)
d.environment_id,
d.id AS deployment_id,
d.type,
d.status,
d.started_at,
d.finished_at,
d.started_by_user->>'email' AS started_by
FROM envzero_deployments d
ORDER BY d.environment_id, d.started_at DESC;
SELECT
d.environment_id,
d.type,
d.status,
d.started_at,
d.failed_command,
d.error
FROM envzero_deployments d
WHERE d.status IN ('FAILURE', 'TIMEOUT', 'INTERNAL_FAILURE')
AND d.started_at > NOW() - INTERVAL '7 days'
ORDER BY d.started_at DESC;
SELECT
e.name AS environment_name,
e.organization_id,
COUNT(r.*) AS resource_count
FROM envzero_environments e
LEFT JOIN envzero_deployments d ON d.environment_id = e.id
LEFT JOIN envzero_deployment_resources r ON r.deployment_id = d.id
GROUP BY e.id, e.name, e.organization_id
ORDER BY resource_count DESC NULLS LAST;
SELECT
drift_status,
COUNT(*) AS environment_count
FROM envzero_environments
GROUP BY drift_status
ORDER BY environment_count DESC;
SELECT
provider,
COUNT(*) AS account_count
FROM envzero_cloud_accounts
GROUP BY provider
ORDER BY account_count DESC;
SELECT
m.module_name,
m.module_provider,
m.repository,
m.organization_id,
m.author->>'email' AS author_email
FROM envzero_modules m
ORDER BY m.organization_id, m.module_name;
SELECT
p.id,
p.name,
p.organization_id,
p.repository,
p.path,
p.created_at,
p.updated_at
FROM envzero_approval_policies p
ORDER BY p.organization_id, p.name;
SELECT
organization_id,
COUNT(*) AS team_count
FROM envzero_organization_teams
GROUP BY organization_id
ORDER BY team_count DESC;
SELECT
t.organization_id,
t.repository,
COUNT(*) AS template_count
FROM envzero_templates t
GROUP BY t.organization_id, t.repository
ORDER BY template_count DESC;