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

Adding site/s via the API to newly created ASNs #11899

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

Originally created by @bctiemann on GitHub (Dec 5, 2025).

Originally assigned to: @bctiemann on GitHub.

NetBox version

v4.4.7

Feature type

Data model extension

Proposed functionality

Feature request from a customer. A customer has recently noted, that when creating a new ASN via the NetBox API. They are unable to allocate the site/s as you can when creating the same object through the UI for NetBox.

Use case

Looking at the REST API documentation you can only add the following when creating an ASN;

asn, rir, comments, tenant, description and tags.

You can however add this separately to the individual site/s themselves, by either creating or editing those objects within the REST API using the relevant fields.

Could we add this ability to ASNs in reverse, so that sites can be assigned during creation and when editing them with the API?

Database changes

No response

External dependencies

No response

Originally created by @bctiemann on GitHub (Dec 5, 2025). Originally assigned to: @bctiemann on GitHub. ### NetBox version v4.4.7 ### Feature type Data model extension ### Proposed functionality Feature request from a customer. A customer has recently noted, that when creating a new ASN via the NetBox API. They are unable to allocate the site/s as you can when creating the same object through the UI for NetBox. ### Use case Looking at the REST API documentation you can only add the following when creating an ASN; asn, rir, comments, tenant, description and tags. You can however add this separately to the individual site/s themselves, by either creating or editing those objects within the REST API using the relevant fields. Could we add this ability to ASNs in reverse, so that sites can be assigned during creation and when editing them with the API? ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featurecomplexity: mediumnetbox labels 2025-12-29 21:51:20 +01:00
adam closed this issue 2025-12-29 21:51:20 +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 complexity: medium netbox status: accepted 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#11899
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?