Closed Spaceman1701 closed 1 year ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.
We have some automation around the auto-generated api documentation and this is causing some issues for us. Could someone point me in the right direction on what might have caused this? I'm happy to take a stab at fixing it.
I tested on v3.3.9 and v3.4.0 and this seems to have been fixed. In v3.3.9 dns_name__empty is missing and in v3.4.0+:
.
NetBox version
v3.3.9
Python version
3.8
Steps to Reproduce
/ipam/ip-address
in the swagger REST API docs and notice thatdns_name__empty
is listed as a parameter/api/ipam/ip-addresses/?dns_name__empty=0
and/api/ipam/ip-addresses/?dns_name__emtpy=1
and observe that the query parameter has the desired effectExpected Behavior
The
/ipam/ip-addresses
endpoint should list thedns_name__empty
query parameter in the Swagger API DocsObserved Behavior
The Swagger API docs are missing the
dns_name__emtpy
query parameter forGET /ipam/ip-addresses
in the Swagger docs. The actual API still seems to honor this parameter. I've observed this in Netbox 3.3.9.This is easy to observe on the demo instance: https://demo.netbox.dev/api/ipam/ip-addresses/?dns_name__empty=1 https://demo.netbox.dev/api/ipam/ip-addresses/?dns_name__empty=0