hohoaisan / export-env-action

GitHub Action that exports .env file variables to job env

Export variables from .env file to job env

Can be useful if you want to use .env file as a storage of constants among multiple workflows.

Examples

Simple case:

# constants.env file

VAR1=abc
VAR2=def

- uses: cardinalby/export-env-action@v2
  with:
    envFile: 'constants.env'    
  
# env.VAR1 == 'abc'
# env.VAR2 == 'def'

Expand variables

# constants.env file

PROTOCOL=https
HOST=example.com
PORT=8080
URI=${PROTOCOL}://${HOST}:${PORT}

- uses: cardinalby/export-env-action@v2
  with:
    envFile: 'constants.env'    
    expand: 'true'
  
# env.PROTOCOL == 'https'
# env.HOST == 'example.com'
# env.PORT == '8080'
# env.URI == 'https://example.com:8080'

Do not export:

# constants.env file

VAR1=abc
VAR2=def

- uses: cardinalby/export-env-action@v2
  id: exportStep
  with:
    envFile: 'constants.env'
    export: 'false'
  
# env.VAR1 == ''
# env.VAR2 == ''
# steps.exportStep.outputs.VAR1 == 'abc'
# steps.exportStep.outputs.VAR2 == 'def'

Inputs

🔸 envFile Required

Path to env file to parse.

🔹 expand Default: false

If true, "expands" variables:

VAR_1=aaa
VAR_2=${VAR_1}_bbb

Will lead to following exported variables: VAR1 = aaa, VAR2 = aaa_bbb.

🔹 expandWithJobEnv Default: false

If true, "expands" variables considering step (job) env variables (in addition to variables defined in the same env file). It means, ${GITHUB_RUN_ATTEMPT} in a variable value will be substituted by the value of $GITHUB_RUN_ATTEMPT job env variable.

🔹 export Default: true

Export variables to a job environment. If false, all variables will be set as an action outputs instead.

🔹 secret Default: false

Register all parsed envs as secret and will get masked from logs

Outputs

If export is false then has an individual output for each variable from env file (where output name equals variable name).