Leo Kirchner

Thanks for submitting! This would need to be handled in - `DiffSync.add` - `DiffSync.update` - `DiffSync.get_or_instantiate` - `DiffSync.get_or_add_model_instance` - `DiffSync.update_or_instantiate` - `DiffSync.update_or_add_model_instance` As such, its probably best to handle this...

> I guess this assumes this, doesn't it?: Yes, thanks. Updated.

> I presume you are already referencing this, but in case not: https://github.com/nautobot/nautobot-plugin-ssot/pull/69/files#diff-d5a05dc0fa5ec399d2b02a105d518741cfc140ec6ce19c4694a3e8c1b8f3e9a7R98 Actually I am not, thanks! From what you linked I can't quite tell in which section you...

Is this maybe something that is SSoT-specific? In diffsync all we really have is two systems - the SoR for a given model can be derived by the direction in...

So _a_ solution to this problem would be statically generating some HTML/Markdown/? from the models and offering meta-level options on the model fields to document whether a user is supposed...

I don't actually need this anymore and don't really have anything to contribute, sorry.

Interesting point. There is https://github.com/networktocode/diffsync/issues/25 which would address this, until then, if you need a quick fix for this, I recommend you do something like ``` class YourAdapter(NautobotAdapter): ... def...

Thanks for elaborating!

Thank you @ftadao - I had already identified this and it is what I meant to convey with the last part of my original issue.

This may be solvable by providing a way to control the scope of the queryset on many to many relationships, i.e. only `tags.filter(name__startswith="some_prefix")`.