Closed n-rodriguez closed 3 weeks ago
To be honest ...
Previously the urls called was api/virtualization/virtual-machines.json but now it throws an error (see below).
I absolutely doubt that. At least not as long as I am using NetBox.
Anyway, the ruby integration you are referring to is not managed by the NetBox project, so you should open an issue with them. It's unlikely that anyone here can help you.
I absolutely doubt that.
you should not ;) this is the url declared in netbox-client-ruby and it has always worked until I've migrated to v4.1.
Anyway, the ruby integration you are referring to is not managed by the NetBox project,
I know, but the url is. I just want to know if something has changed on this side. Thank you!
I don't doubt that it used to work at one point. But AFAIK api/virtualization/virtual-machines.json
has never been an official, documented URL schema, so if it worked it was by coincidence.
But AFAIK
api/virtualization/virtual-machines.json
has never been an official, documented URL schema, so if it worked it was by coincidence.
Thanks for your answer 👍 Now I can make a PR to netbox-client-ruby
to upgrade URLs.
Thank you!
Deployment Type
Self-hosted
NetBox Version
v4.1.1
Python Version
3.11
Steps to Reproduce
Hello!
I'm using netbox-client-ruby to call Netbox API and it seems that collections urls have changed in Netbox v4.1.
Previously the urls called was
api/virtualization/virtual-machines.json
but now it throws an error (see below).Calling
api/virtualization/virtual-machines/
work.It is intentional?
Thank you!
Expected Behavior
No errors should happen
Observed Behavior