Create Env File Job | FlightStack

Create Env File Job

Generates an .env file (or any KEY=VALUE-style file) from FlightStack variables and secrets. Useful for packages like flutter_dotenv that expect a literal file on disk.

Step ref: flightstack/create-env-file@1.0.0.

Configuration

Option	Description	Default
Path	Path to write to (relative to the repo root)	.env
Variables	Names of FlightStack variables / secrets to include	required
Format	dotenv (KEY=value), properties (KEY=value), xml, json	dotenv
Include scope	Which scopes to draw from: repo, pipeline, group, org	all
Comment	Optional header comment prepended to the file	# Generated by FlightStack

Resolution rules

Values are resolved in standard scope order — see variables → scope resolution.

Secrets (variables with isSecret: true) are decrypted on the agent and written into the file with the same permissions as the build workspace (mode 0600).

The file is never persisted to artifact storage and is shredded when the job ends.

Example

steps:
  - name: env
    uses: flightstack/create-env-file@1.0.0
    inputs:
      path: .env
      variables:
        - API_BASE_URL
        - SENTRY_DSN
        - GOOGLE_MAPS_KEY
      format: dotenv

  - name: build
    uses: flightstack/build-android@1.0.0

This writes:

# Generated by FlightStack
API_BASE_URL=https://api.example.com
SENTRY_DSN=https://abc123@sentry.io/1
GOOGLE_MAPS_KEY=AIza...

…then the Build Android step picks it up via flutter_dotenv or similar.

Pairs well with

• Build iOS / Build Android — consume the generated file
• Variables & step outputs — define the source variables
• Secrets management guide — operational patterns