Boris Aelen

Excellent idea! +1

It will be possible to determine which fields are ReadWrite by using meta.Definitions like this ``` ❯ isctl get meta definition --filter "Name eq 'fabric.PortMode'" --select Properties -o json |...

I'm seeing the same behavior with other MO's, for example fabric.Vlan fabric.SwitchProfile fabric.PortMode These are all nested policies and don't seem to have an organization attached to them, but they...

You can get the right unique identifiers for each MO from meta.Definition Could we leverage this for deciding when to update an MO instead of creating one? ``` ❯ isctl...

Same issue, different MO code ```yaml ClassId: resource.Group Name: IMM-Troubleshooting #settings Selectors: - ClassId: resource.Selector Selector: /api/v1/asset/DeviceRegistrations?$filter=Moid in('') ``` First apply works. Second apply tries to create it again with...

Adding myself to this thread as I'm also eager to use this feature. For now it could be helpful to update the error message so it's clear Tado X is...

Another delete order issue FATA[0003] Error while destroying MOs: error executing operation: request failed: 400 Bad Request: Cannot delete policy 'IMM-LinkAggr' as it is referenced by 'Uplink Port Channel' under...