LogoLogo
  • Welcome to Release
  • Getting started
    • Quickstart
    • Create an account
    • Prepare to use Release
    • Create an application
      • Create custom application
      • Create from template
      • Servers vs runnables
    • Create an environment
  • Guides and examples
    • Domains and DNS
      • Manage domains
      • DNS and nameservers
        • Configure GoDaddy
        • Configure Cloudflare
        • Configure Namecheap
        • Other DNS hosts
      • Routing traffic
    • Example applications
      • Full stack voting app
      • Flask and RDS counter app
      • Static site with Gatsby
      • Golang with Postgres and Nginx
      • WordPress with MySQL
      • Spring and PostgreSQL
      • Terraform and Flask
      • OpenTelemetry demo
      • Load balancer with hostname
      • Static JavaScript service
      • SSH bastion access to services
      • ngrok and OAuth for private tunnels
      • Using OAuth Proxy
      • Hybrid Docker and static site
      • App Imports: Connecting two applications
      • Example library
    • Running instances
      • Cron jobs
      • Jobs
      • Using Helm charts
      • Using terminal
      • Viewing logs
      • Troubleshooting
        • ImagePullBackoff error
        • CrashLoopBackoff error
        • Exit codes
        • OOM: out of memory
    • Advanced guides
      • Containers guide
      • Application guide
      • Kubernetes guide
      • Create a cluster
      • Upgrade a cluster
      • Managing node groups
      • Patch node groups
      • Hostnames and rules
      • Serve traffic on multiple ports
      • Configure access to your K8s cluster
      • Designing for multiple environments
      • Microservices architecture
      • Monitoring your clusters
      • Performance tuning
      • Visibility and monitoring
      • Working with data
        • Container-based data
        • Seeding and migration
        • Cloud-provided data
        • Golden images
        • Third party
      • Pausing Instant Datasets
        • Application pausing schedules
        • Pause/resume environments
      • Infrastructure as code
        • Terraform
  • Reference documentation
    • Account settings
      • Account info
      • Managing users
      • Build settings
        • Build arguments
        • Build SSH keys
      • Add integrations
      • View clusters and cloud integrations
      • Add datasets
      • Environment handles
    • Workflows in Release
      • Stages of workflows
      • Serial deployments
      • Parallel deployments
      • Rolling deployments
      • Rainbow deployments
    • Networking
      • Network architecture (AWS)
      • Network architecture (GCP)
      • Ingresses
      • IP addresses
      • Cloud-provided services
      • Third-party services
    • Release environment versioning
    • Application settings
      • Application Template
        • Schema definition
      • Default environment variables
      • GitHub
      • Pull requests
      • GitOps
      • Just-in-time file mounts
      • Primary App Link
      • Create application FAQ
      • App-level build arguments
      • Parameters
      • Workspaces
    • End-to-end testing
    • Environment settings
      • Environment configuration
      • Environment variables
        • Environment variable mappings
        • Secrets vaults
        • Using Secrets with GitOps
        • Kubernetes Secrets as environment variables
        • Managing legacy Release Secrets
    • Environment expiration
    • Environment presets
    • Instant datasets on AWS
    • Instant datasets on GCP
    • Instant dataset tasks
      • Tonic Cloud
      • Tonic On-Premise
    • Cloud resources
    • Static service deployment
    • Helm
      • Getting started
      • Version-controlled Helm charts
      • Open-source charts
      • Building Docker images
      • Ingress and networking
      • Configuration
    • GitOps
    • The .release.yaml file
    • Docker Compose conversion support
    • Reference examples
      • Adding and removing services
      • Managing service resources
      • Adding database containers to the Application Template
      • Stock Off-The-Shelf Examples
    • Release API
      • Account Authentication
      • Environments API
        • Create
        • Get
        • Setup
        • Patch
      • User Authentication
      • Environment Presets API
        • Get Environment Preset List
        • Get Environment Preset
        • Put Environment Preset
  • Background concepts
    • How Release works
  • Frequently asked questions
    • Release FAQ
    • AWS FAQ
    • Docker FAQ
    • JavaScript FAQ
  • Integrations
    • Integrations overview
      • Artifactory integration
      • Cloud integrations (AWS)
        • AWS guides
        • Grant access to AWS resources
        • AWS how to increase EIP quota
        • Control your EKS fleet with systems manager
        • Managing STS access
        • AWS Permissions Boundaries
        • Private ECR Repositories
        • Using an Existing AWS VPC
        • Using an Existing EKS Cluster
      • Docker Hub integration
      • LaunchDarkly integration
      • Private registries
      • Slack integration
      • Cloud integrations (GCP)
        • GCP Permissions Boundary
      • Datadog Agent
      • Doppler Secrets Manager
      • AWS Secrets Management
    • Source control integrations
      • GitHub
        • Pull request comments
        • Pull request labels
        • GitHub deployments
        • GitHub statuses
        • Remove GitHub integration
      • Bitbucket
      • GitLab
    • Monitoring and logging add-ons
      • Datadog
      • New Relic
      • ELK (Elasticsearch, Logstash, and Kibana)
  • Release Delivery
    • Create new customer integration
    • Delivery guide
    • Release to customer account access controls
    • Delivery FAQs
  • Release Instant Datasets
    • Introduction
    • Quickstart
    • Security
      • AWS Instant Dataset security
    • FAQ
    • API
  • CLI
    • Getting started
    • Installation
    • Configuration
    • CLI usage example
    • Remote development environments
    • Command reference
      • release accounts
        • release accounts list
        • release accounts select
      • release ai
        • release ai chat
        • release ai config-delete
        • release ai config-init
        • release ai config-select
        • release ai config-upsert
      • release apps
        • release apps list
        • release apps select
      • release auth
        • release auth login
        • release auth logout
      • release builds
        • release builds create
      • release clusters
        • release clusters exec
        • release clusters kubeconfig
        • release clusters shell
      • release datasets
        • release datasets list
        • release datasets refresh
      • release deploys
        • release deploys create
        • release deploys list
      • release development
        • release development logs
        • release development start
      • release environments
        • release environments config-get
        • release environments config-set
        • release environments create
        • release environments delete
        • release environments get
        • release environments list
        • release environments vars-get
      • release gitops
        • release gitops init
        • release gitops validate
      • release instances
        • release instances exec
        • release instances logs
        • release instances terminal
  • Release.ai
    • Release.ai Introduction
    • Getting Started
    • Release.ai Templates
    • Template Configuration Basics
    • Using GPU Resources
    • Custom Workflows
    • Fine Tuning LlamaX
    • Serving Inference
Powered by GitBook
On this page
  • Description
  • Examples
  • Options
  • Options inherited from parent commands
  • Related

Was this helpful?

  1. CLI
  2. Command reference
  3. release environments

release environments create

Command reference doc for the Release CLI

Create an ephemeral environment and automatically deploy it (by default)

Description

Create an ephemeral environment for the given application.

Unless the --skip-deploy flag is passed, the environment will be automatically deployed.

If the --wait flag is passed, the command will exit with a non-zero exit code if the deploy fails.

If image overrides are specified, they will be used instead of the default built images for the service.

It is possible to override the default environment variables by using the --env-vars flag.

Environment variables may be set by using the --env-vars flag. To set an environment variable for all jobs and services, use the syntax "KEY=VALUE". To override a variable for a specific service use the syntax "services.my-service-name.KEY=VALUE".

release environments create [flags]

Examples


Create a new ephemeral environment and trigger a deployment asynchronously:
> release environments create

Create a new ephemeral environment without deploying it:
> release environments create --skip-deploy

Create a new ephemeral environment and wait until it is deployed before exiting:
> release environments create --app backend --wait

Stream deployment logs to stderr while deploying:
> release environments create --app backend --wait --verbose

Get environment details as JSON:
> release environments create --app backend --branch main --wait --verbose -o json > ./environment.json

Override default image for a service:
> release environments create --app backend --image-overrides api=myrepo/api:latest,worker=myrepo/worker:latest

Override default image for a jobs and services with type qualifiers:
> release environments create --app backend --image-overrides jobs.migrate=myrepo/migrate:latest,services.api=myrepo/api:latest

Override environment variables:
> release environments create --app backend --env-vars DB_URL=postgres://host/db,services.api.NODE_ENV=test

Alternative syntax supporting quoted values:
> release environments create --app backend --env-vars "FOO=value with spaces" --env-vars "BAR=value with spaces"

Options

--account <string>

Account name or ID (default: $RELEASE_ACCOUNT or "account" in config file)

--app <string>

App name or ID (default: $RELEASE_APP or "app" in config file)

--branch <string>

Branch name to track

--context <string>

Name of the cluster to deploy the environment to (overrides default context from Application Template)

--domain <string>

Domain to use for this environment's public URLs (overrides default domain from Application Template)

--env-vars <stringToString>

One or more comma separated env var pairs (example: defaults.MY_VAR1=x,services.api.MY_VAR2=y

--image-overrides <stringToString>

One or more comma separated service image overrides pairs. example: api=myrepo/api:latest,worker=myrepo/worker:latest

-o, --output <string>

Set the output format (table | json | json-pretty)

--skip-deploy

Skip deploying the newly created environment

--verbose

Verbose log output

--wait

Wait for environment deploy to complete before exiting

Options inherited from parent commands

--config <string>

config file (default is $HOME/.release.yaml)

--debug

enable debug logging

Related

Previousrelease environments config-setNextrelease environments delete

Last updated 15 days ago

Was this helpful?

- Manage environments

release environments