Kurach Alexander

@LefterisJP I can

Here is existing Tenant ``` { "count": 1, "next": null, "previous": null, "results": [ { "id": 84, "url": "https://netbox.site/api/tenancy/tenants/84/", "display": "test", "name": "test", "slug": "test-sync", "group": null, "description": "", "comments":...

thats the main issue - slug was changed by sync update. It sent PATH with slug = name ``` Updating NetBox 'tenant' object 'test' with data: {'slug': 'test', ```

If question is about why I've created Tenant by hands: I've got ansible playbook that creates all the tenants, and in our env we have different names and slug, including...

Example: Tenant Name: Simple_IS Tenant Slug: u001-simpl after sync slug will be 'simple-is' Example2: Tenant Name: Простая ИС Tenant slug: u002-simpl2 after sync slug will be '-'

So expected behaviour for me look like If tenant exists - just assosiate VM with it, do not rewrite tenant if tenant not exists - create tenant with autoslug and...

> True, it is pretty ignorant to assume objects are named using roman letters. Agree, but Managers wants to see 'TRUE NAMES' in RU. Nevertheless the case is not about...

sad but no "reopen" button)