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

circuits.circuittermination is not listed in choices API for cable:termination_a/b_type #2570

New Issue
Closed
opened 2025-12-29 18:20:02 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:20:02 +01:00
Owner
Copy Link

Originally created by @shanemadden on GitHub (May 1, 2019).

Environment

  • Python version: 3.5.2
  • NetBox version: 2.5.10 / 2.6 dev

Steps to Reproduce

  1. Create a cable with one end connected to the A or Z termination of a circuit
  2. View that cable in the API, confirming that termination_a_type or termination_b_type is returned as circuits.circuittermination
  3. View the /dcim/_choices/ endpoint, confirm that cable:termination_a_type does not have circuits.circuittermination listed.

Expected Behavior

Return a circuit termination 'choice' table in the _choices API for cable:termination_a_type/cable:termination_b_type:

{
  "label": "circuit termination",
  "value": "circuits.circuittermination"
},

Observed Behavior

Only dcim.* object types are shown as choices for cable:termination_a_type/cable:termination_b_type

Originally created by @shanemadden on GitHub (May 1, 2019). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.5.2 * NetBox version: 2.5.10 / 2.6 dev <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a wrapper like pynetbox. --> ### Steps to Reproduce 1. Create a cable with one end connected to the A or Z termination of a circuit 2. View that cable in the API, confirming that `termination_a_type` or `termination_b_type` is returned as `circuits.circuittermination` 3. View the `/dcim/_choices/` endpoint, confirm that `cable:termination_a_type` does not have `circuits.circuittermination` listed. <!-- What did you expect to happen? --> ### Expected Behavior Return a circuit termination 'choice' table in the _choices API for `cable:termination_a_type`/`cable:termination_b_type`: { "label": "circuit termination", "value": "circuits.circuittermination" }, <!-- What happened instead? --> ### Observed Behavior Only `dcim.*` object types are shown as choices for `cable:termination_a_type`/`cable:termination_b_type`
adam added the type: bugstatus: accepted labels 2025-12-29 18:20:02 +01:00
adam closed this issue 2025-12-29 18:20:02 +01:00
adam commented 2025-12-29 18:20:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 2, 2019):

I was trying to figure out why this wasn't causing issues when connecting a cable to a circuit termination. It's because the cable creation forms currently (in v2.5) only allow connecting a cable from a circuit termination to some device component; the "B" side is never a circuit termination. Hence why this was missed.

@jeremystretch commented on GitHub (May 2, 2019): I was trying to figure out why this wasn't causing issues when connecting a cable to a circuit termination. It's because the cable creation forms currently (in v2.5) only allow connecting a cable _from_ a circuit termination _to_ some device component; the "B" side is never a circuit termination. Hence why this was missed.
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: 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#2570
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?