I have explored few things to find whether we can solve this issue without introducing new schema.
My observation so far is:
1. for member-update shcema is not used for validation and status is validated at [1]. So if we used "oneOf" shcema and added schema definition for update then we need to get rid of this existing validation as well.
2. We can use existing schema for member-create api with minimal changes in create method of RequestDeserializer.
Hi Brian,
I have explored few things to find whether we can solve this issue without introducing new schema.
My observation so far is:
1. for member-update shcema is not used for validation and status is validated at [1]. So if we used "oneOf" shcema and added schema definition for update then we need to get rid of this existing validation as well.
2. We can use existing schema for member-create api with minimal changes in create method of RequestDeserial izer.
Please let me know your opinion about the same.
[1] https:/ /github. com/openstack/ glance/ blob/master/ glance/ domain/ __init_ _.py#L322