Add location to power feeds #8676

New Issue

adam · 2025-12-29T20:39:45+01:00

adam commented

2025-12-29 20:39:45 +01:00

Originally created by @dreng on GitHub (Sep 26, 2023).

NetBox version

v3.6.2

Feature type

Data model extension

Proposed functionality

I propose to add a field "location" to power feeds.

Use case

Since power feeds are physical devices in a physical environment, it is a logical consequence to relate them to a location (like devices, power panels, racks etc).

Database changes

New foreign key field is needed for the power feed model.

External dependencies

No response

Originally created by @dreng on GitHub (Sep 26, 2023). ### NetBox version v3.6.2 ### Feature type Data model extension ### Proposed functionality I propose to add a field "location" to power feeds. ### Use case Since power feeds are physical devices in a physical environment, it is a logical consequence to relate them to a location (like devices, power panels, racks etc). ### Database changes New foreign key field is needed for the power feed model. ### External dependencies _No response_

adam added the type: feature pending closure labels 2025-12-29 20:39:45 +01:00

adam closed this issue

2025-12-29 20:39:45 +01:00

adam commented

2025-12-29 20:39:46 +01:00

@cpmills1975 commented on GitHub (Sep 27, 2023):

PowerFeeds can already be located in a rack. I guess it makes sense that a feed could exist outside of a rack, but if in a rack, the location is presumably derivable from that?

If a rack is defined, the location should be unset in order to prevent issues if a rack location is updated. But if no rack is defined, perhaps the feed could reference a location?

@cpmills1975 commented on GitHub (Sep 27, 2023): PowerFeeds can already be located in a rack. I guess it makes sense that a feed could exist outside of a rack, but if in a rack, the location is presumably derivable from that? If a rack is defined, the location should be unset in order to prevent issues if a rack location is updated. But if no rack is defined, perhaps the feed could reference a location?

adam commented

2025-12-29 20:39:46 +01:00

@dreng commented on GitHub (Sep 28, 2023):

PowerFeeds can already be located in a rack. I guess it makes sense that a feed could exist outside of a rack, but if in a rack, the location is presumably derivable from that?

If a rack is defined, the location should be unset in order to prevent issues if a rack location is updated. But if no rack is defined, perhaps the feed could reference a location?

This is a very common scenario, e.g. with devices. So this is just a copy/paste of an already implemented idea.

@dreng commented on GitHub (Sep 28, 2023): > PowerFeeds can already be located in a rack. I guess it makes sense that a feed could exist outside of a rack, but if in a rack, the location is presumably derivable from that? > > If a rack is defined, the location should be unset in order to prevent issues if a rack location is updated. But if no rack is defined, perhaps the feed could reference a location? This is a very common scenario, e.g. with devices. So this is just a copy/paste of an already implemented idea.

adam commented

2025-12-29 20:39:46 +01:00

@github-actions[bot] commented on GitHub (Dec 28, 2023):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Dec 28, 2023): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).

adam commented

2025-12-29 20:39:46 +01:00

@github-actions[bot] commented on GitHub (Jan 27, 2024):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jan 27, 2024): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

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

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#8676