/v1/bequeath-your-data-and-die is a IndividualService in each application that helps transferring data and subscriptions from old-release to new-release.
In implementation, it is understood that during the service flow between old-release to new-release or to RegistryOffice, if any callback is failed, bequeathing process is expected to be terminated at that point.
But, there is no documentation for that behavior in OAS file. So, can we add a description in /v1/bequeath-your-data-and-die :: callback section to explain this behavior.
/v1/bequeath-your-data-and-die is a IndividualService in each application that helps transferring data and subscriptions from old-release to new-release.
In implementation, it is understood that during the service flow between old-release to new-release or to RegistryOffice, if any callback is failed, bequeathing process is expected to be terminated at that point.
But, there is no documentation for that behavior in OAS file. So, can we add a description in /v1/bequeath-your-data-and-die :: callback section to explain this behavior.