starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-03-02 12:30:06 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add function to trim whitespaces in export templates via jinja environment settings #10309

New Issue
Closed
opened 2025-12-29 21:29:46 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:29:46 +01:00
Owner
Copy Link

Originally created by @w1tht0uchp4d on GitHub (Oct 1, 2024).

Originally assigned to: @renatoalmeidaoliveira on GitHub.

NetBox version

3.7.5

Feature type

Change to existing functionality

Proposed functionality

The goal is to achieve feature parity between the [Provisioning --> Config Templates edit] and [Customization --> Export Templates dialog]. In config templates it is possible to use jinja environment parameters, in export templates it is not.
It's also the same behavior in Netbox v4.1.2 (checked via demo application).

Use case

I'm currently implementing a custom export template, which exports prefixes, their assigned VLANs and some custom fields. I'm aware that part of this, is also achievable via the csv export function, but I want to add some semantic sugar via the power of Jinja, like adding first host address, last host address, ...
The messy white space handling with jinja, unfortunately destroys the formatting of the csv.

Database changes

None required?

External dependencies

None?

Originally created by @w1tht0uchp4d on GitHub (Oct 1, 2024). Originally assigned to: @renatoalmeidaoliveira on GitHub. ### NetBox version 3.7.5 ### Feature type Change to existing functionality ### Proposed functionality The goal is to achieve feature parity between the [Provisioning --> Config Templates edit] and [Customization --> Export Templates dialog]. In config templates it is possible to use jinja environment parameters, in export templates it is not. It's also the same behavior in Netbox v4.1.2 (checked via demo application). ### Use case I'm currently implementing a custom export template, which exports prefixes, their assigned VLANs and some custom fields. I'm aware that part of this, is also achievable via the csv export function, but I want to add some semantic sugar via the power of Jinja, like adding first host address, last host address, ... The messy white space handling with jinja, unfortunately destroys the formatting of the csv. ### Database changes None required? ### External dependencies None?
adam added the status: acceptedtype: featurenetboxcomplexity: low labels 2025-12-29 21:29:46 +01:00
adam closed this issue 2025-12-29 21:29:47 +01:00
adam commented 2025-12-29 21:29:47 +01:00
Author
Owner
Copy Link

@pl0xym0r commented on GitHub (Oct 7, 2024):

Both ConfigTemplate and ExportTemplate inherits from ExportTemplatesMixin

In ConfigTemplate there are params/methods like:
environment_params
def render()
def _get_environment()

Idk if it's too much for export templates but would it be great to move such params/functions to ExportTemplatesMixin ? Or modify utilities.jinja2.py ? At least, use the same enviroment creation for both cases.

@pl0xym0r commented on GitHub (Oct 7, 2024): Both ConfigTemplate and ExportTemplate inherits from ExportTemplatesMixin In ConfigTemplate there are params/methods like: environment_params def render() def _get_environment() Idk if it's too much for export templates but would it be great to move such params/functions to ExportTemplatesMixin ? Or modify utilities.jinja2.py ? At least, use the same enviroment creation for both cases.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label complexity: low netbox status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10309
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?