Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/cuchi/jinja2-action
Use the Jinja2 template engine as a GitHub action
https://github.com/cuchi/jinja2-action
hacktoberfest jinja2
Last synced: 12 days ago
JSON representation
Use the Jinja2 template engine as a GitHub action
- Host: GitHub
- URL: https://github.com/cuchi/jinja2-action
- Owner: cuchi
- Created: 2020-02-07T17:17:00.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2023-11-09T17:49:34.000Z (7 months ago)
- Last Synced: 2024-05-07T15:57:41.821Z (16 days ago)
- Topics: hacktoberfest, jinja2
- Language: Python
- Homepage:
- Size: 29.3 KB
- Stars: 43
- Watchers: 2
- Forks: 24
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
Lists
- awesome-workflows - Apply templates with Jinja2 - Use the Jinja2 template engine to generate files from templates. (Community Resources / Utility)
- awesome-actions - Apply templates with Jinja2 - Use the Jinja2 template engine to generate files from templates. (Community Resources / Utility)
- awesome-actions - Apply templates with Jinja2 - Use the Jinja2 template engine to generate files from templates. (Community Resources / Utility)
- fucking-awesome-actions - Apply templates with Jinja2 - Use the Jinja2 template engine to generate files from templates. (Community Resources / Utility)
- awesome-actions-fork - Apply templates with Jinja2 - Use the Jinja2 template engine to generate files from templates. (Community Resources / Utility)
- awesome-actions - Apply templates with Jinja2 - Use the Jinja2 template engine to generate files from templates. (Community Resources / Utility)
- awesome-actions - Apply templates with Jinja2 - Use the Jinja2 template engine to generate files from templates. (Community Resources / Utility)
README
[](https://github.com/cuchi/jinja2-action/releases/latest)
[](https://github.com/marketplace/actions/jinja2-action)
Jinja2 is a fast and straightforward templating engine. You can use this action
to easily run it in your GitHub workflows.
# Using input variables
```yml
- name: Setup nginx
uses: cuchi/[email protected]
with:
template: infra/nginx.conf.j2
output_file: infra/nginx.conf
strict: true
variables: |
server_host=staging.example.com
timeout=30s
```
# Using data files
```yml
- name: Setup nginx
uses: cuchi/[email protected]
with:
template: infra/nginx.conf.j2
output_file: infra/nginx.conf
data_file: staging_config.json
data_format: json # Will try to guess from the extension instead (unnecessary in this case)
```
# Using environment variables
```yml
- name: Setup nginx
uses: cuchi/[email protected]
with:
template: infra/nginx.conf.j2
output_file: infra/nginx.conf
env:
SERVER_HOST: staging.example.com
```
Environment variables are used this way in the template file:
```
{{ env['SERVER_HOST'] }} <-- This is always strict
```
```
{{ env.get('SERVER_HOST') }} <-- This is never strict, and displays `None` if you don't specify a default value
```
# See also
- [Jinja2 docs](https://jinja.palletsprojects.com/)