dopplerhq / universal-import

Doppler's Universal Import button

Universal Import

Use Universal Import to push secrets directly to engineering services and production infrastructure with the click of a button.

Interested in becoming a Universal Import partner? Visit the Universal Import Hub for more information and to follow the download and installation steps. There you will also find additional information on how it works for the end user alongside FAQs.

@dopplerhq/universal-import

This monorepo holds all Doppler Universal Import packages. Users will generally not want to consume this directly - instead, you should install one of the following child packages:

Core

• @dopplerhq/universal-import-core

React

• @dopplerhq/universal-import-react

Development scripts

These scripts are used for the development of the Doppler Universal Import button components.

NPM Script	Description
npm run dev	Runs all builds in watch mode for interactive development
npm run clean	Removes all build artifacts
npm run build	Generates production builds for all workspaces
npm run build:github-action	Generates production builds for all workspaces (only for github actions)

Required environment variables

This project leverages the Doppler CLI to inject the following environment variables:

• DOPPLER_DASHBOARD_URL must be set as an environment variable for the core package.
• UNIVERSAL_IMPORT_KEYS_URL must be set for post compilation replacement of static values in the core package.

universal-import's Issues

Unable to decrypt universal import payload

We're using @dopplerhq/universal-import-core to build an integration with an internal admin tool to push secrets over to Doppler.

Locally, the connection works fine - trigger successfully renders the Doppler import screen.

In production, the connection renders "Unable to decrypt universal import payload". An example request ID for debugging purposes: 48aed283-6bd5-4956-ac3e-5de84d6a03b8

In both cases, we can see a fetch request being made to https://keys.doppler.com/universal-import/latest.json?cpv=1.0.0 which, in both cases, returns:

{
    "keyId": "dea124b0-a69f-464a-870b-317f9ccaf65b",
    "publicKey": "4x+ohnrLt42vE3lIq2y6Nozs/KI9lAYkREhb56grxhg="
}

Any ideas?