JinjaTurtle

JinjaTurtle is a command-line tool that helps turn existing native configuration files into reusable configuration-management templates.

By default it generates:

• a Jinja2 template; and
• an Ansible defaults YAML file containing the variables used by that template.

It can also generate ERB templates and Puppet Hiera-style YAML data for Puppet workflows.

JinjaTurtle does not try to replace configuration-management tools. Its job is to speed up the boring first pass: take a real config file, discover the values inside it, replace those values with variables, and write the corresponding variable data beside the template.

How it works

JinjaTurtle examines a source config file and keeps the original structure as much as possible.

For the default Jinja2/Ansible mode:

1. The config file is parsed.
2. Variable names are generated from the config keys and paths.
3. Those variable names are prefixed with --role-name, which should usually match your Ansible role name.
4. A Jinja2 template is generated with values replaced by {{ variable }} expressions.
5. An Ansible defaults YAML file is generated with those variables and the original values.

For ERB/Puppet mode:

1. The same parse/flatten/loop analysis is used.
2. An ERB template is generated with Puppet-style instance variables such as <%= @memory_limit %>.
3. The variables file is written as Puppet Hiera-style data, such as php::memory_limit: 256M.
4. If --puppet-class is supplied, that class name is used as the Hiera namespace while --role-name remains the local variable prefix.

By default, the generated variable data and template are printed to stdout. Use --defaults-output and --template-output to write them to files.

Jinja2 / Ansible example

Say you have a php.ini file and you are inside an Ansible role with defaults/ and templates/ directories:

jinjaturtle php.ini \
  --role-name php \
  --defaults-output defaults/main.yml \
  --template-output templates/php.ini.j2

Given a source value such as:

memory_limit = 256M

JinjaTurtle will produce a template value like:

memory_limit = {{ php_memory_limit }}

and defaults data like:

php_memory_limit: 256M

ERB / Puppet example

Use --template-engine erb when you want Puppet ERB output:

jinjaturtle php.ini \
  --role-name php \
  --template-engine erb \
  --defaults-output data/common.yaml \
  --template-output templates/php.ini.erb

Given the same source value:

memory_limit = 256M

JinjaTurtle will produce an ERB template value like:

memory_limit = <%= @memory_limit %>

and Hiera-style data like:

php::memory_limit: 256M

The --defaults-output option name is retained for CLI compatibility, but in ERB mode the file is intended to be Puppet Hiera data rather than Ansible role defaults.

JinjaTurtle does not generate Puppet classes or file resources. A Puppet module, should still declare the class parameters and call the template, for example with Puppet's template() function.

Using --puppet-class

Most direct usage can simply use the same value for the role name and Puppet class name:

jinjaturtle php.ini --role-name php --template-engine erb

This creates Hiera keys such as:

php::memory_limit: 256M

and local ERB variables such as:

<%= @memory_limit %>

For generated systems, it can be useful to make --role-name more specific while keeping the Hiera keys under the real Puppet class. For example:

jinjaturtle php.ini \
  --role-name php_etc_php_ini \
  --puppet-class php \
  --template-engine erb

In that case the variable prefix can stay file-specific, while the Hiera data is still written under php::....

What sort of config files can it handle?

JinjaTurtle supports common structured and semi-structured config formats:

• TOML
• YAML
• INI-style files
• JSON
• XML
• Postfix main.cf
• systemd unit files, such as *.service, *.socket, *.timer, and related unit types
• OpenSSH-style config files, including ssh_config, sshd_config, and common *.conf snippets detected as SSH config

For ambiguous extensions such as *.conf, JinjaTurtle uses lightweight content sniffing. You can always force a handler with --format.

For YAML, XML, TOML, INI-style, and other supported structured files, JinjaTurtle will attempt to generate loops when a repeated structure looks homogeneous enough. If it is not confident, it falls back to flattened scalar variables.

Some very complex files will still need manual cleanup. The goal is to speed up conversion into Jinja2 or ERB templates, not to guarantee a perfect final module without review.

JSON, quoting, and type preservation

JinjaTurtle tries to preserve rendered config types.

For JSON, it uses JSON-aware expressions rather than plain string substitution. This avoids generating invalid JSON such as:

{"enabled": True}

when the correct rendered JSON should be:

{"enabled": true}

In Jinja2 mode this uses Ansible-style JSON filters. In ERB mode it emits Ruby JSON generation where required, for example:

<% require 'json' -%>
{
  "enabled": <%= JSON.generate(@enabled) %>
}

That is expected for JSON ERB templates.

Can I convert multiple files at once?

Yes. Pass a directory instead of a single file and JinjaTurtle will convert the files it understands in that directory.

jinjaturtle ./config-dir \
  --role-name myrole \
  --defaults-output defaults/main.yml \
  --template-output templates/

Use --recursive to recurse into subdirectories.

In folder mode, variables for multiple files of the same type are grouped under an items-style structure in the generated YAML so that the resulting templates can be used with loops in Ansible.

For example:

- name: Render configs
  template:
    src: config.j2
    dest: "/somewhere/{{ item.id }}"
  loop: "{{ myrole_items }}"

How to install it

Ubuntu/Debian apt repository

sudo mkdir -p /usr/share/keyrings
curl -fsSL https://mig5.net/static/mig5.asc | sudo gpg --dearmor -o /usr/share/keyrings/mig5.gpg
echo "deb [arch=amd64 signed-by=/usr/share/keyrings/mig5.gpg] https://apt.mig5.net $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/mig5.list
sudo apt update
sudo apt install jinjaturtle

Fedora

sudo rpm --import https://mig5.net/static/mig5.asc

sudo tee /etc/yum.repos.d/mig5.repo > /dev/null << 'EOF'
[mig5]
name=mig5 Repository
baseurl=https://rpm.mig5.net/$releasever/rpm/$basearch
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://mig5.net/static/mig5.asc
EOF

sudo dnf upgrade --refresh
sudo dnf install jinjaturtle

From PyPI

pip install jinjaturtle

From this git repository

Clone the repo and then run inside the clone:

poetry install

AppImage

Download the AppImage from the Releases page, make it executable, and put it on your $PATH.

Full usage info

usage: jinjaturtle [-h] [-r ROLE_NAME] [--recursive]
                   [-f {ini,json,toml,yaml,xml,postfix,systemd,ssh}]
                   [-d DEFAULTS_OUTPUT] [-t TEMPLATE_OUTPUT]
                   [--template-engine {jinja2,erb}]
                   [--puppet-class PUPPET_CLASS]
                   config

Convert a config file into an Ansible defaults file and Jinja2 template.

positional arguments:
  config                Path to a config file OR a folder containing supported
                        config files. Supported: .toml, .yaml/.yml, .json,
                        .ini/.cfg/.conf, .xml, ssh_config/sshd_config

options:
  -h, --help            show this help message and exit
  -r, --role-name ROLE_NAME
                        Role name / variable prefix. In Jinja2 mode this is
                        usually the Ansible role name. In ERB mode it is used
                        as the local variable prefix. Defaults to jinjaturtle.
  --recursive           When CONFIG is a folder, recurse into subfolders.
  -f, --format {ini,json,toml,yaml,xml,postfix,systemd,ssh}
                        Force config format instead of auto-detecting from
                        filename.
  -d, --defaults-output DEFAULTS_OUTPUT
                        Path to write the generated variable YAML. If omitted,
                        it is printed to stdout.
  -t, --template-output TEMPLATE_OUTPUT
                        Path to write the generated config template. If omitted,
                        it is printed to stdout.
  --template-engine {jinja2,erb}
                        Template syntax to generate. Defaults to jinja2. Use
                        erb for Puppet templates.
  --puppet-class PUPPET_CLASS
                        Puppet class / Hiera namespace to use with
                        --template-engine erb. Defaults to --role-name.

Additional supported formats

JinjaTurtle also templates some common bespoke config formats:

• Postfix main.cf (main.cf) → --format postfix
• systemd unit files (*.service, *.socket, etc.) → --format systemd
• OpenSSH config (ssh_config, sshd_config, and detected snippets) → --format ssh

For ambiguous extensions like *.conf, JinjaTurtle uses lightweight content sniffing. You can always force a specific handler with --format.

Security model

JinjaTurtle is frequently pointed at config files that were harvested from real systems, where some content may be influenced by an untrusted party (a hostname, a login banner, a GECOS comment, a "Managed by ..." note). It is therefore designed so that source content cannot turn into executable template code.

Two guarantees matter:

1. Values are data, never code. Every config value is replaced with a {{ variable }} placeholder in the template, and the original value is stored separately in the defaults/Hiera data. When the template is later rendered, the placeholder prints the value as a literal string; Jinja2 does not recursively render the contents of a variable, so a payload sitting inside a value (for example motd = {{ salt['cmd.run']('id') }}) is inert.

2. Verbatim text is neutralised. To preserve formatting, JinjaTurtle copies comments, blank lines, headers and any unrecognised lines from the source into the template. Any template metacharacters in that copied text ({{ }}, {% %}, {# #} for Jinja2; <% %> for ERB) are escaped so they render as the literal characters the author wrote, rather than executing.

Consumer responsibilities

The value guarantee above relies on the downstream renderer being single-pass, which is the normal case:

• Ansible: rendering a template with template:/ansible.builtin.template is single-pass. For defence in depth, treat the generated defaults as untrusted input — Ansible already does not re-template variable contents by default. If you build your own var structures from this data and pass them through additional templating, mark untrusted values with the !unsafe tag so they are never re-evaluated.
• Salt: use the generated file as a file.managed template (template: jinja). Do not place JinjaTurtle output where Salt would render it a second time as part of SLS/pillar rendering, which is a separate Jinja pass and would re-evaluate any embedded expressions.
• Puppet/ERB: render with the standard template()/epp() flow.

In short: render JinjaTurtle output exactly once. Do not feed it back through another templating pass.

IMPORTANT: Always review both the original config files, then the resulting templates generated by JinjaTurtle, before integrating them into your config management system!

Found a bug, have a suggestion?

You can e-mail me; see pyproject.toml for details. You can also contact me on the Fediverse:

https://goto.mig5.net/@mig5