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

API - Get selection options from dropdowns. (For example interface types) #11307

New Issue
Closed
opened 2025-12-29 21:43:21 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:43:21 +01:00
Owner
Copy Link

Originally created by @powerscooter on GitHub (Jun 23, 2025).

NetBox version

v4.2.3

Feature type

Other

Proposed functionality

Hello, this is just an idea.
For example, we have a website where we can change the type of an interface, among other things. (So that the interface is of type 10GE).

At the moment, you have to manually enter the options you can send to Netbox into the tool. If you had the possibility to retrieve these options via an API from Netbox, you would not have to maintain these options in external tools. This would remove a lot of maintenance work.

Image

Use case

So that you have the possibility to retrieve all possible options from Netbox as well, so that you can load them dynamically in external tools. (name and friendly_name)

Thank you in advance! :-)

Database changes

No response

External dependencies

No response

Originally created by @powerscooter on GitHub (Jun 23, 2025). ### NetBox version v4.2.3 ### Feature type Other ### Proposed functionality Hello, this is just an idea. For example, we have a website where we can change the type of an interface, among other things. (So that the interface is of type 10GE). At the moment, you have to manually enter the options you can send to Netbox into the tool. If you had the possibility to retrieve these options via an API from Netbox, you would not have to maintain these options in external tools. This would remove a lot of maintenance work. <img width="671" alt="Image" src="https://github.com/user-attachments/assets/b799554a-dbc2-41fa-afce-e93327c23233" /> ### Use case So that you have the possibility to retrieve all possible options from Netbox as well, so that you can load them dynamically in external tools. (name and friendly_name) Thank you in advance! :-) ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:43:21 +01:00
adam closed this issue 2025-12-29 21:43:21 +01:00
adam commented 2025-12-29 21:43:21 +01:00
Author
Owner
Copy Link

@markkuleinio commented on GitHub (Jun 24, 2025):

See the OPTIONS call: https://github.com/netbox-community/netbox/discussions/17896

@markkuleinio commented on GitHub (Jun 24, 2025): See the OPTIONS call: https://github.com/netbox-community/netbox/discussions/17896
adam commented 2025-12-29 21:43:21 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Jun 25, 2025):

Thanks @markkuleinio ! I think you nailed it.

@powerscooter , if you have further questions or challenges with the OPTIONS call that was mentioned, I would suggest starting a conversation in the Help Wanted discussion area.

@jnovinger commented on GitHub (Jun 25, 2025): Thanks @markkuleinio ! I think you nailed it. @powerscooter , if you have further questions or challenges with the OPTIONS call that was mentioned, I would suggest starting a conversation in the [Help Wanted discussion](https://github.com/netbox-community/netbox/discussions/new?category=help-wanted) area.
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#11307
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?