Releases: scaleway/python-netboxapi
v1.1.7
v1.1.5
v1.1.4
v1.1.2
v1.1.1
v1.1.0
v1.1.0
-
Fix foreign keys behavior: now, when a foreign key is detected, the attribute will be transformed as a mapper targeting the foreign object. Black magic is done by using properties to fetch this object in a JIT way: accessing the attribute for the first time will trigger a request to fetch it, and put it in a local cache to avoid any new request for next accesses.
-
Fix serialization of netbox choices: when using
put()
on an object containing a netbox enum (or "choice"), the integer value will be cherry-picked from the dict, then sent to netbox. Not ideal for now, could be improved later, but at least works. -
Handle specific cases when a mapper cannot be generated after a
POST
. Typically, a GET on/ipam/prefixes/{id}/available-prefixes/
returns objects without ID. It is now handled, and will return the json as received. -
post()
in mappers now handles mappers as foreign keys. Doingm.post(foo=bar)
whenbar
is aNetboxMapper
is now possible, and will automatically use its id.
Documentation will be added and updated relatively to these changes.
v1.1.0b1
v1.1.0b1
-
Fix foreign keys behavior: now, when a foreign key is detected, the attribute will be transformed as a mapper targeting the foreign object. Black magic is done by using properties to fetch this object in a JIT way: accessing the attribute for the first time will trigger a request to fetch it, and put it in a local cache to avoid any new request for next accesses.
-
Fix serialization of netbox choices: when using
put()
on an object containing a netbox enum (or "choice"), the integer value will be cherry-picked from the dict, then sent to netbox. Not ideal for now, could be improved later, but at least works. -
Handle specific cases when a mapper cannot be generated after a
POST
. Typically, a GET on/ipam/prefixes/{id}/available-prefixes/
returns objects without ID. It is now handled, and will return the json as received.
Documentation will be added and updated relatively to these changes.
v1.0.1
v1.0.0
v1.0.0
- Fully compatible with Netbox 2.0 (GET, POST, PUT, DELETE for mappers)
- Fix issues with URL schemas
- Use routes for NetboxAPI requests instead of complete URL (break backward compatibility)
- NetboxAPI
url
attribute now has to contain the entire URI of the netbox api (netbox.example.com/api
) instead of only the TLD (netbox.example.com
). It will be more flexible if netbox changes its API route (break backward compatibility)