Update for Ansible NetBox Collection to Support 'role' Field Change #1110
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
When attempting to add a new device into NetBox via Ansible, the task fails due to a change in NetBox v3.6.0. In this version, the device_role field on the Device model has been renamed to role. For backward compatibility the field name "device_role" still exist.
This change has not been reflected in the latest Ansible Galaxy NetBox Collection. As a result, when trying to use the updated "role" field, the module throws an error, insisting on using the "device_role" key.
NetBox version: v3.6.3
netbox.netbox collection version: v3.14.0
netbox.netbox version: v0.1.0
Behavior
While adding new device to NetBox via Ansible its throws the following error
fatal: [localhost]: FAILED! => {"changed": false, "msg": "{"role":["This field is required."]}"}
Discussion: Benefits
Ensures compatibility with NetBox v3.6.0 and later.
Prevents unnecessary errors and confusion related to the changed field name.
Changes to the Documentation
Proposed Release Note Entry
Update netbox.netbox.netbox_device to support 'role' Field Change
devel
branch.