Remove a Block <>vNET associations after vNET IP range change that does not fully match the Block CIDR

[rshamsz]

Is your feature request related to a problem? Please describe.
Create a Block and associate a VNETs that falls under the Block CIDR to it.
Change the vNET IP range
Under Configure > Associate , there is an error under Prefix column "ErrNotFound"
Under Discovery > vNETS, IPAM still shows the associations , even though the vNET IP range is updated

Describe the solution you'd like
Automatically, Remove the block <> vNET associations, if all the new IP range of a vnet does not fall under the CIDR of the previously associated Block

Describe alternatives you've considered
Shows a better error messages on both places :
Under Configure > Associate
Under Discovery > vNETS

[DCMattyG]

Hi d-one7 (@rshamsz), I'm acknowledging this is a highly requested feature and I'm working on it as we speak. Hopefully we'll have something ready to test shortly.

Thank you so much for reaching out with this feature request!