starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add option to import custom configuration from configuration.py #8874

New Issue
Closed
opened 2025-12-29 20:42:24 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:42:24 +01:00
Owner
Copy Link

Originally created by @drobnymichal on GitHub (Nov 23, 2023).

NetBox version

v3.6.5

Feature type

New functionality

Proposed functionality

Add the ability to import settings from configuration.py other than what is defined in settings.py.

Use case

I am developing a new NetBox plugin that adds some middleware to NetBox. This middleware requires a special configuration, which it looks for in the settings.py file.

In our organization, we have solved this by editing the settings.py file directly. However, this is impossible from a sustainability point of view because this file is changed between releases.

Database changes

None.

External dependencies

None.

Originally created by @drobnymichal on GitHub (Nov 23, 2023). ### NetBox version v3.6.5 ### Feature type New functionality ### Proposed functionality Add the ability to import settings from configuration.py other than what is defined in settings.py. ### Use case I am developing a new NetBox plugin that adds some middleware to NetBox. This middleware requires a special configuration, which it looks for in the settings.py file. In our organization, we have solved this by editing the settings.py file directly. However, this is impossible from a sustainability point of view because this file is changed between releases. ### Database changes None. ### External dependencies None.
adam added the type: feature label 2025-12-29 20:42:24 +01:00
adam closed this issue 2025-12-29 20:42:24 +01:00
adam commented 2025-12-29 20:42:24 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Nov 23, 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.

@abhi1693 commented on GitHub (Nov 23, 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.
adam commented 2025-12-29 20:42:25 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 27, 2023):

I'll go ahead and nip this in the bud: We aren't going to allow arbitrary modifications to the content of settings.py. To do so would be extremely irresponsible and open the application to myriad potential issues.

However, this is impossible from a sustainability point of view because this file is changed between releases.

If by "impossible," you mean it would impose a slight burden on you, then yes. But if you need to modify core settings to accommodate some third party software, I'm afraid that yes, you'll need to be responsible for testing and maintaining those changes over time.

@jeremystretch commented on GitHub (Nov 27, 2023): I'll go ahead and nip this in the bud: We aren't going to allow arbitrary modifications to the content of `settings.py`. To do so would be extremely irresponsible and open the application to myriad potential issues. > However, this is impossible from a sustainability point of view because this file is changed between releases. If by "impossible," you mean it would impose a slight burden on you, then yes. But if you need to modify core settings to accommodate some third party software, I'm afraid that yes, you'll need to be responsible for testing and maintaining those changes over time.
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 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#8874
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?