1. Docs
  2. Pulumi ESC
  3. Get started
  4. Import environments

Pulumi ESC: Import Environments


    There may be scenarios where the value you need to retrieve is stored in a different environment file. For example, imagine you are building a system that integrates with a third-party service such as:

    • a payment provider
    • weather data provider
    • a content-management system

    In the development environment, you might be integrating with the sandbox or development endpoint of the third-party service, while in the testing environment, you might be integrating with the production endpoint. Both endpoints may share the same base URL.

    Image showing same base URL and different endpoints

    Since this base URL would be the same across environments, it would be more efficient to define it once in one place rather than multiple times across multiple environment files.

    With Pulumi ESC, you can import other environments into your environment file and make use of the imported configuration values and secrets. Similar to values, imports is a top-level key you will need to define in the environment file, meaning the syntax to create an import looks like the following:

      - environment-name-1
      - environment-name-2

    Import an environment

    To demonstrate how this works, you will need to create a second environment. For the purposes of this guide, we will name this new environment app-global-config. In this environment, replace the placeholder content with the following configuration:

      ENDPOINT_URL: "https://wordsapiv1.p.rapidapi.com/"

    Then, open your first environment (e.g. my-dev-environment) via the Pulumi console or the ESC CLI and add the following configuration to the top of your file:

      - app-global-config

    Your updated environment file should look similar to the following:

    # Example contents of my-dev-environment
      - app-global-config
      myEnvironment: "development"
          ciphertext: ZXNjeAA....

    You should now see "ENDPOINT_URL": "https://wordsapiv1.p.rapidapi.com/" in the environment preview pane. This indicates that this value was successfully imported from the app-global-config environment, and you can now retrieve this value in the same way as the other values that are manually defined in this environment.

    You can test this out by retrieving the imported value via the console or the CLI. Refer to the Store and Retrieve Secrets guide for the steps on how to do this.

    Import via the Table view

    Alternatively, you can import environments using the Table view of the Pulumi console. Navigate to the Table view of your environment and click the Import button under the Imports section. You will be presented with a dropdown list of environments that you can import. Search for the name of the environment you want to import and select it. Then click Import.

    To view the imported values, you will need to open your environment.

    You can import multiple environments and reorder them. The order of the imported environments is important because if you have two environments that have the same name for a key/path, then the last imported environment will override the value of that key/paths for any environments that are imported before it. This behavior can be useful for scenarios where you need to intentially override the value of a particular key/path.

    In the next section, you will learn how to run local commands without manually configuring local secrets.

      Introducing Pulumi Copilot - Intelligent Cloud Management