Jathan McCollum
Jathan McCollum
Hey let's keep this moving! Let's get this updated for the latest release and get the tests working.
It appears we may want to wait until DRF 3.6.4 which should be adding support for the generation of response schemas. See: https://github.com/encode/django-rest-framework/issues/4502
DRF 3.6.4 is out! For additional context, one of the primary use-cases for a standardized schema is generating a Golang client using [go-swagger](https://github.com/go-swagger/go-swagger). I've started experimenting with using a project...
Ah yes. I knew that just didn't update the ticket. Thank you!
The NSoT GUI needs a lot of work and it's likely a bad bug. We decided not to set the timezone by default, to leave that up to people to...
Let's stick with Networks since that is your use-case, and this is something I think could be solved by the current IPAM feature set in NSoT. I am, however, interested...
I like that direction. The concept of an "unallocated resource" is certainly more tangible. In the case of Networks, it means it just doesn't exist in the database. I think...
Once upon a time we talked about having a “Location” object at one point internally at DBX but it kind of fell flat. This is another thing we are currently...
The correct solution involves moving all of the attribute "patching" from the `pynsot.app.App.process_attributes()` method into the NSoT backend. This way, the API can do the right thing with regard to...
PATCH support was added to API in #155. Now we can talk about partial updates of attributes, if that's still a desirable feature.