Add Jinja Filters to Customization like scripts #8061

Closed
opened 2025-12-29 20:31:50 +01:00 by adam · 3 comments
Owner

Originally created by @peterbaumert on GitHub (May 15, 2023).

NetBox version

v3.5.1

Feature type

Change to existing functionality

Proposed functionality

To be able to add new Jinja filters just like Scripts/Reports, so one doesn't have to put them in configuration.py and therefore keeping this file cleaner.

Use case

The new Config Rendering feature is very useful but there are a few thing "missing" which you can add via Jinja Filters. This would make that task much easier and one would be able to store those filter in datasources as well instead of in the configuration file.

Database changes

Not sure sorry

External dependencies

No response

Originally created by @peterbaumert on GitHub (May 15, 2023). ### NetBox version v3.5.1 ### Feature type Change to existing functionality ### Proposed functionality To be able to add new Jinja filters just like Scripts/Reports, so one doesn't have to put them in configuration.py and therefore keeping this file cleaner. ### Use case The new Config Rendering feature is very useful but there are a few thing "missing" which you can add via Jinja Filters. This would make that task much easier and one would be able to store those filter in datasources as well instead of in the configuration file. ### Database changes Not sure sorry ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:31:50 +01:00
adam closed this issue 2025-12-29 20:31:50 +01:00
Author
Owner

@jeremystretch commented on GitHub (May 15, 2023):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (May 15, 2023): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
Author
Owner

@peterbaumert commented on GitHub (May 20, 2023):

I do not really know what else i could add. I am not familiar with netbox development, hence i cant really tell you what would be needed.

From a UI perspective it would be exactly the same as for Scripts. Just that it will be automatically added as Jinja Filters so one does not have to "polute" the configuration.py with those methods.

@peterbaumert commented on GitHub (May 20, 2023): I do not really know what else i could add. I am not familiar with netbox development, hence i cant really tell you what would be needed. From a UI perspective it would be exactly the same as for Scripts. Just that it will be automatically added as Jinja Filters so one does not have to "polute" the configuration.py with those methods.
Author
Owner

@jeremystretch commented on GitHub (May 25, 2023):

I do not really know what else i could add. I am not familiar with netbox development, hence i cant really tell you what would be needed.

In that case, please start by opening a discussion to collaborate with others to flesh out your idea into a detailed implementation plan. Your single sentence under "proposed functionality" does not constitute an actionable proposal.

@jeremystretch commented on GitHub (May 25, 2023): > I do not really know what else i could add. I am not familiar with netbox development, hence i cant really tell you what would be needed. In that case, please start by opening a [discussion](https://github.com/netbox-community/netbox/discussions/new/choose) to collaborate with others to flesh out your idea into a detailed implementation plan. Your single sentence under "proposed functionality" does not constitute an actionable proposal.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8061