NetBox v3.3 has multiple endpoints for dcim.cables (appears as 'AttributeError: object has no attribute "id"')
See original GitHub issueWhen talking to NetBox v3.3, pynetbox v6.6.2 chokes when POSTing to dcim.cable
by raising exception AttributeError: object has no attribute “id”
This is because in NetBox v3.2 and earlier:
{
"id": 1,
"termination_a_type": "circuits.circuittermination",
"termination_a_id": 1,
"termination_a": {
...
}
...
}
Whereas NetBox v3.3 has a list of dicts:
{
"id": 1,
"a_terminations": [
{
"object_type": "dcim.interface",
"object_id": 42,
...
}
]
...
}
Issue Analytics
- State:
- Created a year ago
- Reactions:14
- Comments:9
Top Results From Across the Web
There was a problem with your request. Netboxv3.0.0
<class 'AttributeError'> 'str' object has no attribute 'available_columns' Python version: 3.8.10 NetBox version: 3.0.0. If further assistance is required, ...
Read more >NetBox v3.0 - NetBox Documentation
An IP range must be assigned a status of active, reserved, or deprecated. The REST API implementation for this model also includes an...
Read more >Posts by Year - NetBox.dev
This month I recap the v3.4 beta release and take a detailed look at several new enhancements to the plugins API.
Read more >Pynetbox - NetBox Python API client part 2 - creating objects |
Perfect, to have pynetbox create object we need to specify app and endpoint, just like we did when retrieving information. Then we need...
Read more >v3.2-beta2 - Netbox - Appd8.io
WARNING: NetBox v3.2 requires Python 3.8 or later. Breaking Changes. Automatic redirection of legacy slug-based URL paths has been removed.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve got this on my list to work on next, but will take a while before I can get it updated. If you see any other APIs broken for 3.3, please let me know.
Any updates here?