runtime - all values are allowed, custom serialization rules, still stateless, very complex behavior, too smart for its own good
Desired Behavior
Whereas it is not possible to remove the first and second use cases, the third must be split into a record that can be exposed to external systems and successfully deserialized there.
Existing Behavior
Zone settings exist in three incarnations:
hold
is missing, other values are allowed, immutable, stateless, no behaviorDesired Behavior
Whereas it is not possible to remove the first and second use cases, the third must be split into a record that can be exposed to external systems and successfully deserialized there.
Related Issues
327