-
Notifications
You must be signed in to change notification settings - Fork 216
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
fixing bug #975 #1323
fixing bug #975 #1323
Conversation
This looks good to me, just needs a changelog put into the |
this interface should exist and the ip 10.10.200.31/16 should be added to it
I added the tests and fragment to the PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the contribution!
Yes please do |
I opened issue #1338, you are welcome to come and take a look 😁 |
Thank you for reviewing my code! |
Related Issue
The issue this PR is trying to fix is #975
New Behavior
this pull request changes the data object to include the assigned_object_id and assigned_object_type values.
it takes the interface_id that exists in the interface value and adds an assigned_object_id and an assigned_object_type item.
Contrast to Current Behavior
the current behavior will not assign an IP to the interface.
Discussion: Benefits and Drawbacks
This bug prevents the assigning of an IP to an interface.
it is backwards compatible.
It is worth noting that there is a duplication between the assigned_object and interface values.
In my opinion it is best to deprecate the interface value internally and make people use only the assigned_object value.
Changes to the Documentation
the documentation already states this functionality, it was not implemented but it should have.
Proposed Release Note Entry
netbox_ip_address - Fixed the problem preventing assignment of an IP address to a network interface
Double Check
devel
branch.