Skip to content

Commit 1586766

Browse files
committed
Add doppler-secrets docs
1 parent 5773be4 commit 1586766

File tree

3 files changed

+93
-0
lines changed

3 files changed

+93
-0
lines changed

content/docs/esc/integrations/_index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,7 @@ ESC also integrates with tools like Direnv, Terraform, and Docker to help manage
3030

3131
- [AWS Secrets Manager](/docs/esc/integrations/dynamic-secrets/aws-secrets)
3232
- [Azure KeyVault](/docs/esc/integrations/dynamic-secrets/azure-secrets)
33+
- [Doppler Secrets](/docs/esc/integrations/dynamic-secrets/doppler-secrets)
3334
- [GCP Secrets Manager](/docs/esc/integrations/dynamic-secrets/gcp-secrets)
3435
- [Infisical Secrets](/docs/esc/integrations/dynamic-secrets/infisical-secrets)
3536
- [Vault Secrets Management](/docs/esc/integrations/dynamic-secrets/vault-secrets)

content/docs/esc/integrations/dynamic-secrets/_index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,5 +21,6 @@ To learn how to set up and use each provider, follow the links below. To learn h
2121
| [aws-parameter-store](/docs/pulumi-cloud/esc/providers/aws-parameter-store/) | The `aws-parameter-store` provider enables you to dynamically import parameters from AWS Parameter Store into your Environment. |
2222
| [aws-secrets](/docs/esc/integrations/dynamic-secrets/aws-secrets/) | The `aws-secrets` provider enables you to dynamically import Secrets from AWS Secrets Manager into your Environment. |
2323
| [azure-secrets](/docs/esc/integrations/dynamic-secrets/azure-secrets/) | The `azure-secrets` provider enables you to dynamically import Secrets from Azure Key Vault into your Environment. |
24+
| [doppler-secrets](/docs/esc/integrations/dynamic-secrets/doppler-secrets/) | The `doppler-secrets` provider enables you to dynamically import Secrets from Doppler into your Environment.
2425
| [gcp-secrets](/docs/esc/integrations/dynamic-secrets/gcp-secrets/) | The `gcp-secrets` provider enables you to dynamically import Secrets from Google Cloud Secrets Manager into your Environment. |
2526
| [vault-secrets](/docs/esc/integrations/dynamic-secrets/vault-secrets/) | The `vault-secrets` provider enables you to dynamically import Secrets from HashiCorp Vault into your Environment. |
Lines changed: 91 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,91 @@
1+
---
2+
title: doppler-secrets
3+
title_tag: doppler-secrets Pulumi ESC provider
4+
meta_desc: The doppler-secrets Pulumi ESC Provider enables you to dynamically import secrets from Doppler into your environment.
5+
h1: doppler-secrets
6+
menu:
7+
esc:
8+
identifier: doppler-secrets
9+
parent: esc-dynamic-secrets
10+
weight: 5
11+
aliases:
12+
- /docs/pulumi-cloud/esc/providers/doppler-secrets/
13+
- /docs/esc/providers/doppler-secrets/
14+
---
15+
16+
The `doppler-secrets` provider enables you to dynamically import Secrets from Doppler into
17+
your Environment. The provider will return a map of names to Secrets.
18+
19+
## Example
20+
21+
```yaml
22+
values:
23+
doppler:
24+
login:
25+
fn::open::doppler-login:
26+
oidc:
27+
identityId: 00000000-0000-0000-0000-000000000000
28+
secrets:
29+
fn::open::doppler-secrets:
30+
login: ${doppler.login}
31+
project: example-project
32+
config: dev
33+
get:
34+
api-key:
35+
name: API_KEY
36+
app-secret:
37+
name: APP_SECRET
38+
```
39+
40+
## Configuring OIDC
41+
42+
To learn how to configure OpenID Connect (OIDC) between Pulumi Cloud and Doppler, see
43+
the [OpenID Connect integration](/docs/pulumi-cloud/oidc/provider/doppler/) documentation. Once you have completed
44+
these steps, you can validate that your configuration is working by running either of the following:
45+
46+
* `esc open <org>/<project>/<environment>` command of the [Pulumi ESC CLI](/docs/esc-cli/)
47+
* `pulumi env open <org>/<project>/<environment>` command of the [Pulumi CLI](/docs/install/)
48+
49+
Make sure to replace `<org>`, `<project>`, and `<environment>` with the values of your Pulumi organization and
50+
environment identifier respectively. You should see output similar to the following:
51+
52+
```json
53+
{
54+
"doppler": {
55+
"login": {
56+
"accessToken": "dp.said.XXX..."
57+
},
58+
"secrets": {
59+
"api-key": "my-api-key",
60+
"app-secret": "my-app-secret"
61+
}
62+
}
63+
}
64+
```
65+
66+
## Inputs
67+
68+
| Property | Type | Description |
69+
|----------|--------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|
70+
| `login` | [DopplerSecretsLogin](#dopplersecretslogin) | Credentials to use to log in to Doppler. |
71+
| `project` | string | The project identifier in Doppler |
72+
| `config` | string | The config identifier in Doppler |
73+
| `get` | map[string][DopplerSecretsGet](#dopplersecretsget) | A map from names to secrets to read from Doppler Secrets. The outputs will map each name to the secret's sensitive data. |
74+
75+
### DopplerSecretsLogin
76+
77+
| Property | Type | Description |
78+
|---------------|--------|---------------------------------------------------------------------------------------------------------------------------|
79+
| `accessToken` | string | The access token to use for authentication. |
80+
81+
### DopplerSecretsGet
82+
83+
| Property | Type | Description |
84+
|---------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
85+
| `name` | string | The secret name in Doppler |
86+
87+
### Outputs
88+
89+
| Property | Type | Description |
90+
|----------|--------|-------------------------------------|
91+
| N/A | object | A map of names to imported Secrets. |

0 commit comments

Comments
 (0)