Add scope_name field when doing bulk ipam.prefixes imports

[dhoffend]

NetBox version

v4.2.2

Feature type

Change to existing functionality

Proposed functionality

Add scope_name in addition or as alternative field to scope_id when doing builk ipam.prefix (and others) imports.

Use case

Before updating from v4.1 to v4.2 we noticed the breaking change about the removal of the site field which got replaced by a combination of scope_type and scope_id. I don't question the need for the multipe scope types, but to have a better migration when doing bulk imports it would be nice to have a scope_name field in addition to scope_id. Of course you can only have one field filled (id or name).

Sure this would cause an id-lookup when scope_name is used (like in v4.1) but it would help the transition (we would just have to add scope_type=dcim.site and rename the csv field site to scope_name and continue instead of using numeric ids during mass imports.

Database changes

Not that I know of

External dependencies

None

[KPTheProf]

I second this request, not been able to import using the scope name is major headache for us.
Users will only have the scope name data (i.e. site name if importing a dcim.site), the scope_id is just an internal reference.
I don't understand why this was changed to scope_id in the first place!