It would be nice if the site_tag used allowed for a prepended value to be specified in the PLUGINS_CONFIG settings. Using just the site name as the signifying tag could cause devices that are tagged with that site to inadvertently be delete. It might be better if it were more unique than just the site name which could be used elsewhere for various reasons.
Use Case
Perhaps there could be a specific prepend value for the site_tag, something like this:
Perhaps when the site_tag name is set in the code this value, if present, could be prepended (eg: ACI-site1). If this value isn't specified in the PLUGINS_CONFIG, no value would be prepended and that would allow backwards compatibility to existing deployments with tags without a prepended value.
Environment
Proposed Functionality
It would be nice if the site_tag used allowed for a prepended value to be specified in the PLUGINS_CONFIG settings. Using just the site name as the signifying tag could cause devices that are tagged with that site to inadvertently be delete. It might be better if it were more unique than just the site name which could be used elsewhere for various reasons.
Use Case
Perhaps there could be a specific prepend value for the site_tag, something like this:
PLUGINS_CONFIG = { "nautobot_ssot": { "site_tag_prepend": "ACI-" } }
Perhaps when the site_tag name is set in the code this value, if present, could be prepended (eg: ACI-site1). If this value isn't specified in the PLUGINS_CONFIG, no value would be prepended and that would allow backwards compatibility to existing deployments with tags without a prepended value.