In App class of pynautobot library there is method for retrieving data from '/api/extras/custom-fields/' endpoint. The method has name custom_choices().
And it can make some mess, because Nautobot service actually provide another endpoint "/api/extras/custom-field-choices/". So such naming can be somewhat confusing:
from /api/extras:
Extras API root view
GET /api/extras/
{
...
"custom-field-choices": "http://localhost:8888/api/extras/custom-field-choices/",
"custom-fields": "http://localhost:8888/api/extras/custom-fields/",
...
}
And they return completely different data.
Futhermore, there is no method to get data from "/api/extras/custom-field-choices/". Perhaps it should be implemented.
In
App
class of pynautobot library there is method for retrieving data from '/api/extras/custom-fields/' endpoint. The method has namecustom_choices()
. And it can make some mess, because Nautobot service actually provide another endpoint "/api/extras/custom-field-choices/". So such naming can be somewhat confusing: from /api/extras:And they return completely different data.
Futhermore, there is no method to get data from "/api/extras/custom-field-choices/". Perhaps it should be implemented.