adding a possibility of defining default platform

[pibjndata]

Environment

• Nautobot version: 1.1.3
• aristacv-sync version: 1.0.2

Proposed Functionality

Adding a default platform in the same way as we can add e.g. device_role automatically:

PLUGINS_CONFIG = {

"nautobot_ssot" : {

ADD YOUR SETTINGS HERE

}

"nautobot_ssot_aristacv": {

(...)

"from_cloudvision_default_site": "",

"from_cloudvision_default_device_role": "",

I would like to have a possibility to set a default platform here, the default value could be e.g. EOS in plugin settings. Then all device types should be associated to this device platform.

Use Case

[jdrew82]

@pibjndata Can you clarify your intention on this? There was a bug in the plug-in that was having a Platform created for each device model when there should have only been one for the Arista EOS platform. I've corrected this bug and it now shows as ansible.eos.eos for the name, ansible_eos for the slug, and eos for the NAPALM driver. The thinking is that you can use the name for the Ansible library and the slug for the netmiko library. If you need to translate between these you can easily use something like the lib_mapper function in the netutils library.

[Kircheneer]

I have an adjacent, possibly different suggestion. It would be great if we could configure the name of the platform through the plugin settings. I ran into an issue with @ubajze where the migrations were crashing because we had a platform called "Arista EOS" and this was trying to create a platform called "arista.eos.eos" with the same slug. If we had this, we could have specified that our platform (existing prior to the installation of this app) was called something else than "arista.eos.eos".