From my point of view, setting the attribute to null in the API should suffice to reset it, just like the attribute is set to null for creating a subnet without a gateway.
This would be consistent with the current semantics of the API.
I don't think it was a simple oversight however, since this has some implications on IPAM too.
The discussion about how to reset attribute pertained more the CLI if I recall correctly, and was more about distinguishing clearing from 'reset to default'. On the server side this shouldn't be problematic at all, unless, as it happened in the past, we're planning to change the API for suiting the CLI needs...
From my point of view, setting the attribute to null in the API should suffice to reset it, just like the attribute is set to null for creating a subnet without a gateway.
This would be consistent with the current semantics of the API.
I don't think it was a simple oversight however, since this has some implications on IPAM too.
The discussion about how to reset attribute pertained more the CLI if I recall correctly, and was more about distinguishing clearing from 'reset to default'. On the server side this shouldn't be problematic at all, unless, as it happened in the past, we're planning to change the API for suiting the CLI needs...