Skip to content

Fix device_role to role breaking change in netbox_device module #1062

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

Closed
wants to merge 1 commit into from

Conversation

shaul75
Copy link

@shaul75 shaul75 commented Sep 2, 2023

Updated the Ansible NetBox module to accommodate recent breaking changes in the NetBox API where device_role has been renamed to role. Also made corresponding adjustments in the pynetbox library.

Related Issue

New Behavior

...

Contrast to Current Behavior

...

Discussion: Benefits and Drawbacks

...

Changes to the Documentation

...

Proposed Release Note Entry

...

Double Check

  • I have read the comments and followed the CONTRIBUTING.md.
  • I have explained my PR according to the information in the comments or in a linked issue.
  • My PR targets the devel branch.

Updated the Ansible NetBox module to accommodate recent changes in
the NetBox API where `device_role` has been renamed to `role`.
Also made corresponding adjustments in the pynetbox library to
ensure compatibility.
@rodvand
Copy link
Contributor

rodvand commented Sep 3, 2023

We can't just stop supporting 3.5 and 3.4, so the device_role and role will have to live side by side for a while. We should also note about deprecation on the device_role field.

@FragmentedPacket
Copy link
Contributor

Hi @shaul75,

Thanks for your PR and taking the initiative to submit a fix! As @rodvand stated, we still need to support previous versions so logic must be added to make this change dependent on the version of Netbox.

I created #1066 with the fix for backwards compatibility if you want to check it out.

If you'd like, I can submit a PR into your fork based off of your PR to ensure you get credit for the fix as well. This would obviously delay the fix dependent on our schedules, but figured I'd at least ask.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants