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

Allow configuration of Netbox powerfeed defaults #5591

New Issue
Closed
opened 2025-12-29 19:29:52 +01:00 by adam · 6 comments
adam commented 2025-12-29 19:29:52 +01:00
Owner
Copy Link

Originally created by @gordonjcp on GitHub (Oct 31, 2021).

Originally assigned to: @huntabyte on GitHub.

NetBox version

v3.0.7

Feature type

Change to existing functionality

Proposed functionality

At the moment the POWERFEED_VOLTAGE_DEFAULT, POWERFEED_AMPERAGE_DEFAULT and POWERFEED_MAX_UTILIZATION_DEFAULT are picked up from dcim/constants.py and set for typical US datacentre values.

It would be good to adapt that to allow them to pick up either the defaults in constants.py or defaults supplied from an environment variable or config file instead.

Use case

This would remove a UX "papercut" for users outside of the US.

Database changes

No response

External dependencies

No response

Originally created by @gordonjcp on GitHub (Oct 31, 2021). Originally assigned to: @huntabyte on GitHub. ### NetBox version v3.0.7 ### Feature type Change to existing functionality ### Proposed functionality At the moment the POWERFEED_VOLTAGE_DEFAULT, POWERFEED_AMPERAGE_DEFAULT and POWERFEED_MAX_UTILIZATION_DEFAULT are picked up from dcim/constants.py and set for typical US datacentre values. It would be good to adapt that to allow them to pick up either the defaults in constants.py or defaults supplied from an environment variable or config file instead. ### Use case This would remove a UX "papercut" for users outside of the US. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:29:52 +01:00
adam closed this issue 2025-12-29 19:29:52 +01:00
adam commented 2025-12-29 19:29:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 1, 2021):

I think this makes sense, but it probably lends itself more toward user-configurable preferences. Unfortunately we don't have any real framework in place for that yet. v3.1 will introduce support for toggling certain configuration parameters directly within the UI (see #5883); maybe that's a reasonable stopgap for now.

@jeremystretch commented on GitHub (Nov 1, 2021): I think this makes sense, but it probably lends itself more toward user-configurable preferences. Unfortunately we don't have any real framework in place for that yet. v3.1 will introduce support for toggling certain configuration parameters directly within the UI (see #5883); maybe that's a reasonable stopgap for now.
adam commented 2025-12-29 19:29:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 5, 2021):

Marking this as blocked by #7759 (currently planned for v3.2).

@jeremystretch commented on GitHub (Nov 5, 2021): Marking this as blocked by #7759 (currently planned for v3.2).
adam commented 2025-12-29 19:29:53 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 21, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Feb 21, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:29:54 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 6, 2022):

This should be easily doable now with v3.2 finalized.

@jeremystretch commented on GitHub (Apr 6, 2022): This should be easily doable now with v3.2 finalized.
adam commented 2025-12-29 19:29:54 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 7, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jun 7, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:29:54 +01:00
Author
Owner
Copy Link

@huntabyte commented on GitHub (Jun 20, 2022):

I will work to support this.

My thoughts are to let the user override the default values via the Preferences page under a 'Power' title.

The values would be prepopulated with defaults that match the content but allow a user to select other standards for each option.

Any additional thoughts/concerns on this?

@huntabyte commented on GitHub (Jun 20, 2022): I will work to support this. My thoughts are to let the user override the default values via the Preferences page under a 'Power' title. The values would be prepopulated with defaults that match the content but allow a user to select other standards for each option. Any additional thoughts/concerns on this?
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 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#5591
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?