Asset tag vs source-id about netbox-ssot

[bl4ko]

Yes I agree, I will fix this behaviour.

[bl4ko]

Hello, currently the terms are used in the following way:

• source-id custom field is currently used to store object's id on the source, for example:

  • ovirt: every object has an "id" field, this "id" field from ovirt api is then mapped to source-id custom field in netbox

• asset tag is currently mapped from uuid from the host devices to the netbox asset tag field

  • ovirt: every host has an "uuid" attribute, so this uuid attribute is mapped to netbox asset tag

[TaLoN1x]

but then you can also specify a real asset-tag (that companies use in their inventory) in most hypervisors also and current behaviour conflicts with ability to use this data in relation to a device.

[bl4ko]

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀