Use Jinja2 template engine on multipe files as a GitHub Action.

This action transfrom all local j2 files (recursively) ('*.j2') with the jinja2 library.

• All the detect template will be resolve and named without the j2 extension. For exemple, README.md.j2 becomes README.md.
• Original template file can be keep or not (not keeped by default)
• All gihub contextes are available inside template (github, job, runner, strategy, matrix)
• It is possible to give more input variables to the jinja2 engine in multiple way:
  • From environement variables,
  • From variable given in input,
  • From local data files in multipe possible format (env, yaml, json, ini)
  • From URL source in multipe possible format (env, yaml, json, ini)
• The behaviour of the jinje2 engine on not defined value can be defined

- uses: fletort/jinja2-template-action@v1
  env:
    TEST: my_value

Environment variables are used as with jinja2 cli:

{{ environ('TEST') }}

Or as other contextual GitHub information:

{{ env.TEST }}

- uses: fletort/jinja2-template-action@v1
  with:
    variables: |
      TEST1=mytest
      TEST2=isfunny

- uses: fletort/jinja2-template-action@v1
  with:
    data_file: my_data.json
    data_format: json # can be detected automatically (see below)

Possible data type are: env, yaml, json, ini

EXEMPLE_SMART=yoyo
EXEMPLE_MY_VAR=True

[EXEMPLE]
SMART=yoyo
MY_VAR=True

---
EXEMPLE:
  SMART=yoyo
  MY_VAR=True

{
  "EXEMPLE": {
    "SMART": "yoyo",
    "MY_VAR": True
  }
}

For previous INI, YAML, JSON examples, jinja template will be:

{{ EXEMPLE.SMART }}
{{ EXEMPLE.MY_VAR }}

For previous ENV example, jinja template will be:

{{ EXEMPLE_SMART }}
{{ EXEMPLE_MY_VAR }}

URL can also be used as data source, in the same previous format. The exemple below see the use of a data file from another repository.

- uses: fletort/jinja2-template-action@v1
  with:
    data_url: https://raw.githubusercontent.com/owner/anoter-repo/refs/heads/main/my_var.yml
    data_format: yaml # can be detected automatically (see below)

Some of the contextual information about workflow runs are available inside your jinja Template:

• github
• job
• runner
• strategy
• matrix

As part of an expression, you can access context information using one of two syntaxes. Index syntax: github['sha'] Property dereference syntax: github.sha

{{ github.repository }}
{{ job.status }}
{{ runner.os }}
{{ strategy.job_index }}
{{ matrix.your_matrix_variable_name }}

Note: All strategy information key contains dashes that must me marked as underscore in jinja expression: ${{ strategy.job-index }} becomes {{ strategy.job_index }}.

It is possible to define how jinja 2 engine manage undefined value. Actually only behavior proposed by Jinja2 library can be used: Undefined, ChainableUndefined, DebugUndefined or StrictUndefined.

When a simple variable is not defined:

• Undefined and ChainableUndefined return an empty string
• DebugUndefined keeps the variable name
• StrictUndefined raises en error

When trying to accessing a undefined key of an existing dictionnary:

• Undefined and ChainableUndefined return an empty string
• DebugUndefined write a warning of type {{ no such element: dict object['my_key'] }}
• StrictUndefined raises en error

When trying to accessing a undefined key of an undefined dictionnary:

• Undefined, DebugUndefined and StrictUndefined raises en error
• ChainableUndefined return an empty string

For exemple with the following data:

defined: value
with_key:
  ok: toto

Results are:

All unit test executed on each branch/PR are listed/described on testspace.

Coverage information and history is also avalailable on coveralls.

The scripts and documentation in this project are released under the MIT License