Can we stop trying to make the status field complicated? I'd rather just say "error" and have more detailed field of why it's set to an error versus "this-volume-is-in-error-because-of-this". There is some headaches it yet another field that needs to be updated, but I think we just need an interface for updating state rather than calling the db api.
Can we stop trying to make the status field complicated? I'd rather just say "error" and have more detailed field of why it's set to an error versus "this-volume- is-in-error- because- of-this" . There is some headaches it yet another field that needs to be updated, but I think we just need an interface for updating state rather than calling the db api.