Table: doppler_config - Query Doppler Configurations using SQL
Doppler is a universal secret manager that helps developers manage and securely access secrets such as database credentials, API keys, and tokens. It provides a centralized way to store, access, and manage secrets for various applications and services. Doppler helps ensure that secrets are securely stored and are only accessible to authorized users.
Table Usage Guide
The doppler_config
table provides insights into configurations within Doppler's secret management. As a developer or DevOps engineer, explore configuration-specific details through this table, including secrets, their values, and the projects they belong to. Utilize it to manage and control access to secrets, ensuring that they are only accessible to authorized users.
Examples
Basic info
This query allows users to gain insights into the configurations of their Doppler projects. It can be used to understand the creation date, environment, root, and lock status of each project, which can be useful for project management and security purposes.
select project, name, created_at, environment, root, lockedfrom doppler_config;
select project, name, created_at, environment, root, lockedfrom doppler_config;
Get environment details of each config
Analyze the settings to understand the relationship between environments and their associated configurations. This is useful for auditing purposes and to ensure proper setup of your environments.
select c.name as config_name, c.created_at as config_created_at, c.root, e.name as environment_name, e.created_at as environment_created_at, e.slugfrom doppler_config as c, doppler_environment as ewhere e.slug = c.environment;
select c.name as config_name, c.created_at as config_created_at, c.root, e.name as environment_name, e.created_at as environment_created_at, e.slugfrom doppler_config as c, doppler_environment as ewhere e.slug = c.environment;
List root configs
Explore which configurations are set as root in your projects to gain insights into your system's setup. This is useful for assessing the elements within your environment that may require additional security or permissions due to their root status.
select project, name, created_at, environment, rootfrom doppler_configwhere root;
select project, name, created_at, environment, rootfrom doppler_configwhere root = 1;
List configs that are locked
Discover the configurations that are locked, to understand which project settings are currently unmodifiable. This can be useful in managing project changes and identifying potential bottlenecks in the workflow.
select project, name, created_at, lockedfrom doppler_configwhere locked;
select project, name, created_at, lockedfrom doppler_configwhere locked = 1;
List configs that are created in last 30 days
Explore recent configurations by identifying those created within the past month. This aids in keeping track of changes and updates, ensuring your system remains up-to-date and secure.
select name, created_at, initial_fetch_at, last_fetch_atfrom doppler_configwhere created_at >= now() - interval '30' day;
select name, created_at, initial_fetch_at, last_fetch_atfrom doppler_configwhere created_at >= datetime('now', '-30 day');
Get project details for each config
Discover the segments that provide an overview of each project, including the environment and configuration details. This is useful for understanding the structure and organization of your projects.
select c.name config_name, c.project, c.environment, p.id as project_id, p.created_at as project_created_at, p.slug as project_slugfrom doppler_config as c, doppler_project as pwhere c.project = p.name;
select c.name config_name, c.project, c.environment, p.id as project_id, p.created_at as project_created_at, p.slug as project_slugfrom doppler_config as c, doppler_project as pwhere c.project = p.name;
Schema for doppler_config
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. | |
environment | text | Identifier of the environment that the config belongs to. | |
initial_fetch_at | timestamp with time zone | Date and time of the first secrets fetch. | |
last_fetch_at | timestamp with time zone | Date and time of the last secrets fetch. | |
locked | boolean | Whether the config can be renamed and/or deleted. | |
name | text | = | The name of the config. |
project | text | = | The ID of the project. |
root | boolean | Whether the config is the root of 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_config