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

The "Position" field doesn't resolve the {module} variable in nested modules #11668

New Issue
Open
opened 2025-12-29 21:48:19 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:48:19 +01:00
Owner
Copy Link

Originally created by @tpx-mk on GitHub (Oct 2, 2025).

Originally assigned to: @mrmrcoleman on GitHub.

NetBox Edition

NetBox Community

NetBox Version

4.3.7

Python Version

3.10

Steps to Reproduce

  • Create a module type, e.g. TapeLib Extension module
  • Within the module type create one (or more) module bay(s) with the {module} variable in the position field
  • Create another module type, e.g. TapeLib Drive module
  • Add a module of the first type into some device (e.g. TapeLibrary)
  • Add a module of the second type into a module bay of the first module

Expected Behavior

the {module} variable gets expended not only in the names of the modules and interfaces and the label field but also in the position field

Observed Behavior

the position in the nested moduled shows {module} as text without resolving the variable

Originally created by @tpx-mk on GitHub (Oct 2, 2025). Originally assigned to: @mrmrcoleman on GitHub. ### NetBox Edition NetBox Community ### NetBox Version 4.3.7 ### Python Version 3.10 ### Steps to Reproduce - Create a module type, e.g. _TapeLib Extension module_ - Within the module type create one (or more) module bay(s) with the {module} variable in the _position_ field - Create another module type, e.g. _TapeLib Drive module_ - Add a module of the first type into some device (e.g. TapeLibrary) - Add a module of the second type into a module bay of the first module ### Expected Behavior the {module} variable gets expended not only in the names of the modules and interfaces and the _label_ field but also in the _position_ field ### Observed Behavior the position in the nested moduled shows _{module}_ as text without resolving the variable
adam added the type: bugstatus: acceptednetboxseverity: low labels 2025-12-29 21:48:19 +01:00
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 netbox severity: low status: accepted type: bug
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#11668
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?