netbox/docs/models/extras/configtemplate.md
Renato Almeida de Oliveira fbd6d8c7fc
Closes #17653: Add function to trim whitespaces in export templates via jinja environment settings (#19078)
* Create RenderMixin, and unify template_code rendering and exporting

* Join migrations

* Add DEFAULT_MIME_TE constant

* Move RenderMixin to extras.models.mixins, Rename RenderMixin to RenderTemplateMixin

* Add render_jinja2 to __all__

* Rename ConfigTemplateFilterForm rendering FieldSet

* ConfigTemplate lint

* Simplify ExportTemplate get_context

* Fix table order, and add fields for translations

* Update Serializers

* Update forms, tables, graphQL, API

* Add extra tests for ConfigTemplate and ExportTemplate

* Documentation update

* Fix typo

* Misc cleanup

* Clean up template layouts

---------

Co-authored-by: Jeremy Stretch <jstretch@netboxlabs.com>
2025-04-08 10:37:15 -04:00

2.1 KiB

Configuration Templates

Configuration templates can be used to render device configurations from context data. Templates are written in the Jinja2 language and can be associated with devices roles, platforms, and/or individual devices.

Context data is made available to devices and/or virtual machines based on their relationships to other objects in NetBox. For example, context data can be associated only with devices assigned to a particular site, or only to virtual machines in a certain cluster.

See the configuration rendering documentation for more information.

Fields

Name

A unique human-friendly name.

Data File

Template code may optionally be sourced from a remote data file, which is synchronized from a remote data source. When designating a data file, there is no need to specify template code: It will be populated automatically from the data file.

Template Code

Jinja2 template code, if being defined locally rather than replicated from a data file.

Environment Parameters

A dictionary of any additional parameters to pass when instantiating the Jinja2 environment. Jinja2 supports various optional parameters which can be used to modify its default behavior.

MIME Type

!!! info "This field was introduced in NetBox v4.3."

The MIME type to indicate in the response when rendering the configuration template (optional). Defaults to text/plain.

File Name

!!! info "This field was introduced in NetBox v4.3."

The file name to give to the rendered export file (optional).

File Extension

!!! info "This field was introduced in NetBox v4.3."

The file extension to append to the file name in the response (optional).

As Attachment

!!! info "This field was introduced in NetBox v4.3."

If selected, the rendered content will be returned as a file attachment, rather than displayed directly in-browser (where supported).