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

Allow {module} variable in position field #10827

New Issue
Closed
opened 2025-12-29 21:36:22 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:36:22 +01:00
Owner
Copy Link

Originally created by @mattg66 on GitHub (Feb 28, 2025).

NetBox version

v4.2.4

Feature type

New functionality

Proposed functionality

Allow the {module} variable to be used in the Position field. Currently the text is not parsed and {module} remains as text. The position of the module then has to be manually updated after it has been instantiated into a module within a device.

Image

Use case

When modules have nested modules such as PSUs, it would be useful to have the parent modules position passed down to the child module so that interfaces and ports can be renamed based on their parents position.

Database changes

No response

External dependencies

No response

Originally created by @mattg66 on GitHub (Feb 28, 2025). ### NetBox version v4.2.4 ### Feature type New functionality ### Proposed functionality Allow the {module} variable to be used in the Position field. Currently the text is not parsed and {module} remains as text. The position of the module then has to be manually updated after it has been instantiated into a module within a device. ![Image](https://github.com/user-attachments/assets/59a195cf-d298-4d33-a63a-92b02227aa32) ### Use case When modules have nested modules such as PSUs, it would be useful to have the parent modules position passed down to the child module so that interfaces and ports can be renamed based on their parents position. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:36:22 +01:00
adam closed this issue 2025-12-29 21:36:22 +01:00
adam commented 2025-12-29 21:36:23 +01:00
Author
Owner
Copy Link

@mattg66 commented on GitHub (Feb 28, 2025):

Realised this is implemented with the multiple {module} syntax, the error message for this is confusing.

@mattg66 commented on GitHub (Feb 28, 2025): Realised this is implemented with the multiple {module} syntax, the error message for this is confusing.
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#10827
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?