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

Region-/sitewide defaults for Power #4787

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

Originally created by @martinum4 on GitHub (Apr 19, 2021).

NetBox version

v2.11-beta1

Feature type

Change to existing functionality

Proposed functionality

  • Allow default values Voltage and Amperage to be added to Regions and Sites.

If none is given, the values should be taken from the corresponding "higher" entity.

Example:
Region Germany has 230VAC 50Hz defined as default, it is automatically used for the Subregion of Berlin and all Locations in that Region.

Use case

The proposed functionality makes it faster and easier to add power feeds since the default values match the region the hardware is located in.

Database changes

No response

External dependencies

No response

Originally created by @martinum4 on GitHub (Apr 19, 2021). ### NetBox version v2.11-beta1 ### Feature type Change to existing functionality ### Proposed functionality - Allow default values Voltage and Amperage to be added to Regions and Sites. If none is given, the values should be taken from the corresponding "higher" entity. Example: Region Germany has 230VAC 50Hz defined as default, it is automatically used for the Subregion of Berlin and all Locations in that Region. ### Use case The proposed functionality makes it faster and easier to add power feeds since the default values match the region the hardware is located in. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:20:27 +01:00
adam closed this issue 2025-12-29 19:20:27 +01:00
adam commented 2025-12-29 19:20:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 19, 2021):

Allow Power feeds to be assigned to a Location.

Please open a separate feature request for this.

@jeremystretch commented on GitHub (Apr 19, 2021): > Allow Power feeds to be assigned to a Location. Please open a separate feature request for this.
adam commented 2025-12-29 19:20:28 +01:00
Author
Owner
Copy Link

@martinum4 commented on GitHub (Apr 19, 2021):

Added #6211 as separate proposal.

@martinum4 commented on GitHub (Apr 19, 2021): Added #6211 as separate proposal.
adam commented 2025-12-29 19:20:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 20, 2021):

Allow default values Voltage and Amperage to be added to Regions and Sites.

NetBox doesn't have a mechanism to do this. Could you please elaborate on the specific change(s) you're proposing?

@jeremystretch commented on GitHub (Apr 20, 2021): > Allow default values Voltage and Amperage to be added to Regions and Sites. NetBox doesn't have a mechanism to do this. Could you please elaborate on the specific change(s) you're proposing?
adam commented 2025-12-29 19:20:29 +01:00
Author
Owner
Copy Link

@martinum4 commented on GitHub (Apr 20, 2021):

I'm not a coder so i might be wrong, but apparently the default Voltage is coming from the variable POWERFEED_VOLTAGE_DEFAULT, which is defined in /netbox/dcim/constants.py .

Since there has to be a site selected when defining a new feed anyway the Voltage-field could be autofilled with the voltage after the selection of a site.

@martinum4 commented on GitHub (Apr 20, 2021): I'm not a coder so i might be wrong, but apparently the default Voltage is coming from the variable `POWERFEED_VOLTAGE_DEFAULT,` which is defined in /netbox/dcim/constants.py . Since there has to be a site selected when defining a new feed anyway the Voltage-field could be autofilled with the voltage after the selection of a site.
adam commented 2025-12-29 19:20:29 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 12, 2021):

I'm going to close this for two reasons:

  1. It doesn't make sense to associate a default voltage with a site or region.
  2. There's no mechanism in place to support this, and implementing one would be far more trouble than it's worth.

This is something we can revisit when and if NetBox gets some form of per-user default value persistence mechanism.

@jeremystretch commented on GitHub (May 12, 2021): I'm going to close this for two reasons: 1. It doesn't make sense to associate a default voltage with a site or region. 2. There's no mechanism in place to support this, and implementing one would be far more trouble than it's worth. This is something we can revisit when and if NetBox gets some form of per-user default value persistence mechanism.
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#4787
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?