Table: doppler_environment - Query Doppler Environments using SQL

Doppler is a universal secrets manager that helps developers manage and securely access environment secrets during application development. It provides a secure and scalable solution for storing and retrieving environment-specific configuration data. Doppler Environment is a specific resource within Doppler that represents a unique environment for a project, containing all the environment variables for that specific environment.

Table Usage Guide

The doppler_environment table provides insights into Doppler Environments within a project. As a DevOps engineer, explore environment-specific details through this table, including environment ID, name, and the associated project ID. Utilize it to uncover information about each environment, such as the specific variables stored in each environment, aiding in efficient configuration management and security audits.

Examples

Basic info

Explore which Doppler environments are linked to specific projects, when they were created, and their associated workplace names. This can help assess the organization and distribution of your resources within a project.

select
  id,
  slug,
  name,
  project,
  created_at,
  workplace_name
from
  doppler_environment;

select
  id,
  slug,
  name,
  project,
  created_at,
  workplace_name
from
  doppler_environment;

List environments that are created in the last 30 days

Discover the segments that were established in the past month. This can provide insights into recent project developments and their associated environments, aiding in project management and planning.

select
  id,
  slug,
  name,
  project,
  created_at,
  workplace_name
from
  doppler_environment
where
  created_at >= now() - interval '30 day';

select
  id,
  slug,
  name,
  project,
  created_at,
  workplace_name
from
  doppler_environment
where
  created_at >= datetime('now', '-30 day');

List environments for a specific project

Explore which environments are associated with a specific project. This is useful for understanding the various settings and configurations tied to a particular project, aiding in project management and oversight.

select
  id,
  slug,
  name,
  project,
  created_at,
  workplace_name
from
  doppler_environment
where
  project = 'example-project';

select
  id,
  slug,
  name,
  project,
  created_at,
  workplace_name
from
  doppler_environment
where
  project = 'example-project';

Schema for doppler_environment

Name	Type	Operators	Description
_ctx	jsonb		Steampipe context in JSON form.
created_at	timestamp with time zone		Date and time of the object's creation.
id	text		An identifier for the environment.
initial_fetch_at	timestamp with time zone		Date and time of the first secrets fetch from a config in the environment.
name	text		Name of the environment.
project	text	=	Identifier of the project the environment belongs to.
slug	text	=	A unique identifier for the environment.
sp_connection_name	text	=, !=, ~~, ~~, !~~, !~~	Steampipe connection name.
sp_ctx	jsonb		Steampipe context in JSON form.
title	text		The name of the workplace.
workplace_id	text	=, !=, ~~, ~~, !~~, !~~	The ID of the workplace.
workplace_name	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)" -- doppler

You can pass the configuration to the command with the --config argument:

steampipe_export_doppler --config '<your_config>' doppler_environment