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

Creating object via API doesn't establish relationship to other objects #2328

New Issue
Closed
opened 2025-12-29 17:24:53 +01:00 by adam · 1 comment
adam commented 2025-12-29 17:24:53 +01:00
Owner
Copy Link

Originally created by @tyler-8 on GitHub (Jan 30, 2019).

Environment

  • Python version: 3.6.8
  • NetBox version: v2.5.3 (and v2.5.4)

Steps to Reproduce

Sites

  1. Create a tenant via GUI (or API)
  2. Using API (pynetbox or requests, try to create a site with the tenant_id of your tenant from step 1.
  3. Check in GUI (or via API) for the new site, notice there is no Tenant relationship.

Regions

  1. Create a region via GUI (or API)
  2. Using API (pynetbox or requests, try to create a region with the parent_id of your region from step 1.
  3. Check in GUI (or via API) for the new region, notice there is no parent relationship.

Expected Behavior

The site would be properly associated to the tenant.

Observed Behavior

The tenant & parent region field is left empty/null for the site.

Notes

I'd originally thought this was related to https://github.com/digitalocean/pynetbox/issues/145, but this doesn't work with requests either.

Originally created by @tyler-8 on GitHub (Jan 30, 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.6.8 <!-- Example: 3.5.4 --> * NetBox version: v2.5.3 (and v2.5.4) <!-- Example: 2.5.2 --> <!-- 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 #### Sites 1. Create a tenant via GUI (or API) 2. Using API (`pynetbox` or `requests`, try to create a site with the `tenant_id` of your tenant from step 1. 3. Check in GUI (or via API) for the new site, notice there is no Tenant relationship. #### Regions 1. Create a region via GUI (or API) 2. Using API (`pynetbox` or `requests`, try to create a region with the `parent_id` of your region from step 1. 3. Check in GUI (or via API) for the new region, notice there is no parent relationship. <!-- What did you expect to happen? --> ### Expected Behavior The site would be properly associated to the tenant. <!-- What happened instead? --> ### Observed Behavior The tenant & parent region field is left empty/null for the site. ### Notes I'd originally thought this was related to https://github.com/digitalocean/pynetbox/issues/145, but this doesn't work with `requests` either.
adam closed this issue 2025-12-29 17:24:53 +01:00
adam commented 2025-12-29 17:24:53 +01:00
Author
Owner
Copy Link

@tyler-8 commented on GitHub (Jan 30, 2019):

Well. I feel somewhat silly. When creating an object via the API, use the tenant or parent key and pass the ID, rather than tenant_id or parent_id. I think I knew this at one point and crossed the streams somewhere. Perhaps an improvement to the documentation would help here. I'll tackle that elsewhere.

@tyler-8 commented on GitHub (Jan 30, 2019): Well. I feel somewhat silly. When creating an object via the API, use the `tenant` or `parent` key and pass the ID, rather than `tenant_id` or `parent_id`. I think I knew this at one point and crossed the streams somewhere. Perhaps an improvement to the documentation would help here. I'll tackle that elsewhere.
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
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#2328
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?