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
  • Adding URL Mappers
  • Adding Environment Mappers

Was this helpful?

  1. Build System
  2. Terraform

Mapping URLs/Configs

PreviousVariablesNextUsing Cached Services

Last updated 3 years ago

Was this helpful?

Gallery gives you visibility into your environments by proxying traffic to your environments load balancers/external facing URLs. To enable this behavior for terraform templates, you need to add the appropriate URL mappers.

Adding URL Mappers

Once you add a Terraform service in the templates page, you'll be presented with a modal that lets you customize the terraform service. Go to the URL mappers tab, and click add.

Gallery will proxy traffic from the environment subdomain to the URL specified in the terraform output you provide.

Adding Environment Mappers

Sometimes, you'll need a reference to the infrastructure you created in the post infrastructure creation build step. You can create an environment mapper to enable this. Go to the environment mappings tab, click add, and select a terraform output. You'll be able to access that output in the post-build step in the environment variable that you provide.