From 0fc87ea3e7241d51196cf43af1760c90e3585d77 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Thu, 25 Jun 2026 16:27:59 +0000 Subject: [PATCH] docs: update Doppler and Infisical env group creation flow --- applications/configure/environment-groups.mdx | 8 ++++++++ integrations/doppler.mdx | 17 ++++++++++++----- integrations/infisical.mdx | 16 ++++++++++++---- 3 files changed, 32 insertions(+), 9 deletions(-) diff --git a/applications/configure/environment-groups.mdx b/applications/configure/environment-groups.mdx index fb4ca77..0264925 100644 --- a/applications/configure/environment-groups.mdx +++ b/applications/configure/environment-groups.mdx @@ -27,6 +27,14 @@ You can create a new environment group from the **Env Groups** tab on the Porter Environment group names must be up to 63 characters and may only contain lowercase letters, numbers, and hyphens (`-`). +The create form has a **Type** selector that lets you choose where the values are stored: + +- **Porter** — values are managed in Porter and synced to your cloud provider's secret manager. This is the default. +- **Doppler** — values are pulled from a [Doppler](/integrations/doppler) config. Requires the Doppler integration to be enabled on at least one cluster. +- **Infisical** — values are pulled from an [Infisical](/integrations/infisical) project. Requires the Infisical integration to be enabled on at least one cluster. + +Doppler and Infisical environment groups are read-only in Porter and sync to a single cluster. Porter environment groups can be synced to any number of clusters in the project. + You can also create environment groups from the CLI: diff --git a/integrations/doppler.mdx b/integrations/doppler.mdx index ca1c5bd..86959ac 100644 --- a/integrations/doppler.mdx +++ b/integrations/doppler.mdx @@ -28,11 +28,18 @@ The token will be prefixed with `dp.st.`. ### Create the environment group in Porter -1. On the Doppler integration page in Porter, click **Add Doppler env group**. -2. Fill in the form: - - **Env group name (vanity name for Porter)** — the name you'll use to reference this environment group inside Porter (e.g. `production-doppler`). - - **Doppler service token** — the `dp.st.…` token you generated above. -3. Click **Add Doppler env group**. +Doppler environment groups are created from the same form as any other Porter environment group. + +1. From the Porter dashboard, navigate to the **Env Groups** tab and click **New Env Group**. +2. Enter a **Name** — the name you'll use to reference this environment group inside Porter (e.g. `production-doppler`). +3. For **Type**, select **Doppler**. (This option only appears once the Doppler integration is enabled on at least one cluster.) +4. Paste your **Doppler service token** (the `dp.st.…` token you generated above). +5. Select the **Target cluster** to sync the secrets into. If only one cluster has Doppler enabled, it's preselected. +6. Click **Create environment group**. + + +You can also start from the Doppler integration page and click **Create a Doppler environment group** to deep-link into the create form with **Doppler** preselected. + Add a new Doppler service token modal in the Porter dashboard diff --git a/integrations/infisical.mdx b/integrations/infisical.mdx index ae59f37..44233a9 100644 --- a/integrations/infisical.mdx +++ b/integrations/infisical.mdx @@ -31,16 +31,24 @@ Keep both values handy — you'll paste them into Porter in the next step. ### Create the environment group in Porter -1. On the Infisical integration page in Porter, click **Add Infisical env group**. -2. Fill in the form: - - **Name (for Porter environment group)** — the name you'll use to reference this environment group inside Porter (e.g. `production-infisical`). +Infisical environment groups are created from the same form as any other Porter environment group. + +1. From the Porter dashboard, navigate to the **Env Groups** tab and click **New Env Group**. +2. Enter a **Name** — the name you'll use to reference this environment group inside Porter (e.g. `production-infisical`). +3. For **Type**, select **Infisical**. (This option only appears once the Infisical integration is enabled on at least one cluster.) +4. Fill in the Infisical configuration: - **Project slug** — the slug of the Infisical project to sync from. - **Env slug** — the environment to pull from (e.g. `dev`, `staging`, `prod`). - **Env path** — the secret path within the environment. Defaults to `/`. - **Service URL** — the Infisical API URL. Defaults to `https://app.infisical.com/api`. Set this to your self-hosted Infisical URL if you're not using Infisical Cloud. - **Client ID** — the client ID of the machine identity you created. - **Client Secret** — the client secret of the machine identity. -3. Click **Add Infisical env group**. +5. Select the **Target cluster** to sync the secrets into. If only one cluster has Infisical enabled, it's preselected. +6. Click **Create environment group**. + + +You can also start from the Infisical integration page and click **Create an Infisical environment group** to deep-link into the create form with **Infisical** preselected. + Add a new Infisical integration modal in the Porter dashboard