NeoAnd/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2025-07-27 10:58:37 -06:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity

Update export-templates.md

Browse Source 
Both export templates and config context data are extremely powerful and useful, but it isn't immediately clear how use the two together.  This change adds details on how to use the two together.
This commit is contained in:
tcaiazza 2021-03-25 11:59:34 -04:00 committed by GitHub
parent e9930854c4
commit d66306b990
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/additional-features/export-templates.md
View File

@ -18,6 +18,14 @@ Height: {{ rack.u_height }}U
To access custom fields of an object within a template, use the `cf` attribute. For example, `{{ obj.cf.color }}` will return the value (if any) for a custom field named `color` on `obj`. To access custom fields of an object within a template, use the `cf` attribute. For example, `{{ obj.cf.color }}` will return the value (if any) for a custom field named `color` on `obj`.
Since local_context_data is part of an object, it is immediately available to use in the export template, but if you need the fully rendered context config you'll need to use the function `get_config_context`. For example:
```
{% for server in queryset %}
{% set data = server.get_config_context() %}
{{data.syslog}}
{% endfor %}
```
A MIME type and file extension can optionally be defined for each export template. The default MIME type is `text/plain`. A MIME type and file extension can optionally be defined for each export template. The default MIME type is `text/plain`.
## Example ## Example