Gallery
  • Introduction to Gallery
  • Getting Started
    • Link Your Cloud Provider
    • Create a Template
    • Build an Environment
  • Cloud Integrations
    • AWS
    • GCP
    • Other Cloud Providers
  • Gallery CLI
    • Setup
      • Installation
      • Authentication
  • Build System
    • Overview
    • Project Builds
      • Build Jobs
      • Build Stages
      • .gallery-deploy.yml Docs
    • Terraform
      • Variables
      • Mapping URLs/Configs
      • Using Cached Services
  • Cached Services
    • Overview
    • Defining Cached Services
  • Examples
    • Flask Elastic Beanstalk Quickstart
  • Resources
    • Environments
      • Managing your Environments
      • Environment Teardown
      • Environment Settings
Powered by GitBook
On this page
  • Creating an Environment Variable Set
  • Adding Environment Variables
  • Using Environment Variable Sets

Was this helpful?

  1. Resources
  2. Environments

Environment Settings

PreviousEnvironment Teardown

Last updated 3 years ago

Was this helpful?

You may have different sets of environment variables and secrets depending on the type of environment you wish to spin up (Staging vs PR Review, for example). In order to support this use case, we support configuratble environment variable sets that can be specified when you create an environment.

Creating an Environment Variable Set

To create an environment variable set, go to the template page and the "Env Variables" tab. Click the "New" button and specify a name for the environment variable set.

Adding Environment Variables

Adding environment variables to the set is easy, just specify them in the format ENV_VAR='value' separated by newlines. The file is parsed statically, so you aren't able to use previously defined environment variables in later environment variables.

Using Environment Variable Sets

You can use environment variable sets easily when creating an environment. Just specify the relevant config when you create an environment, and all the environment variables will be usable in any build steps.