-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix device_role -> role and add testing for Netbox 3.6 #1066
Conversation
Could we merge the device_role fix and handle the VC issue in a different PR? |
…ut can be removed eventually.
… further down in code.
I fixed that one as well. There apparently is more breaking changes around IP addresses or maybe it's the code. I will leave this alone for now and keep those two fixes in while you review. |
facing issues with the role msg": "{"role":["This field is required."]}"} , may i know if this has been fixed ? |
do you know when this will be rolled into the next release? |
@rodvand Is there any way to get around the problem for now until the next release? |
Read https://docs.ansible.com/ansible/latest/collections_guide/collections_installing.html and just install it from the develop branch on GitHub. |
Related Issue
device_role
was renamed torole
within the Netbox API for v3.6+Filter for IP Addresses now require
virtual_chassis_member_id
to fetch VC member interfaces anddevice_id
no longer returns the VC member interfaces.Fixes #1061
New Behavior
Compatibility with Netbox APIs but no user changes need to occur.
Proposed Release Note Entry
Fix
device_role
being renamed torole
in Netbox 3.6+ APIChange query params for searching interfaces when we need to find the VC member interfaces.