Support adding/modifying DataFiles via REST API #1387

New Issue

MrUnknownDE · 2026-04-06T00:30:09+02:00

MrUnknownDE commented

2026-04-06 00:30:09 +02:00

Originally created by @tindarid on 8/26/2025

NetBox version

v4.3.6

Feature type

New functionality

Proposed functionality

Allow POST/PUT requests for DataFile endpoints: /api/core/data-files/
This will allow using DataFileLoader from https://github.com/netbox-community/netbox/blob/main/netbox/utilities/jinja2.py, meaning that we can create templates which reference other templates (extends/include/import Jinja2 statements) without defining DataSource

For example:

Having a directory of templates referencing each other, like here: https://github.com/jeremystretch/example-config-templates
new: Create DataFile object per file in the repository (specifying path/contents)
Create ConfigTemplate referencing master templates in the repository (in this example: access-switch.j2)
Rendering of access-switch.j2 works without defining DataSource

Use case

Would allow PUSH-ing templates with import capabilities, instead of PULL-ing them via defined data source: beneficial in certain infrastructure scenarios

Database changes

None: there is an unique constraint on Path already

External dependencies

N/A

*Originally created by @tindarid on 8/26/2025* ### NetBox version v4.3.6 ### Feature type New functionality ### Proposed functionality - Allow POST/PUT requests for DataFile endpoints: `/api/core/data-files/` - This will allow using DataFileLoader from https://github.com/netbox-community/netbox/blob/main/netbox/utilities/jinja2.py, meaning that we can create templates which reference other templates (extends/include/import Jinja2 statements) without defining DataSource For example: * Having a directory of templates referencing each other, like here: https://github.com/jeremystretch/example-config-templates * new: Create DataFile object per file in the repository (specifying path/contents) * Create ConfigTemplate referencing master templates in the repository (in this example: `access-switch.j2`) * Rendering of `access-switch.j2` works without defining DataSource ### Use case Would allow PUSH-ing templates with import capabilities, instead of PULL-ing them via defined data source: beneficial in certain infrastructure scenarios ### Related - Solves: https://github.com/netbox-community/netbox/discussions/15505 - https://github.com/netbox-community/netbox/discussions/13602 - https://github.com/netbox-community/netbox/discussions/13575 ### Database changes None: there is an unique constraint on Path already ### External dependencies N/A

MrUnknownDE closed this issue

2026-04-06 00:30:09 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#1387