When /v1/bequeath-your-data-and-die is executed ,call back "PromptForBequeathingDataCausesRequestForDeregisteringOfOldRelease" should not be executed if new-application is of same release and same application name

[vanithavalluripalli9]

Problem Description:

When we trigger /v1/bequeath-your-data-and-die for oldRelease as application of same release and same application name got deployed in new-application-address and new-application-port .

Then during call back "PromptForBequeathingDataCausesRequestForDeregisteringOfOldRelease" , deregister-application will be sent with current-application-name and current-release-number which is same as new-application-name and new-release-number in this case , it will lead to end of subscriptions .

Solution: Call back "PromptForBequeathingDataCausesRequestForDeregisteringOfOldRelease" should not be executed if new-application is of same release and same application name.

[vanithavalluripalli9]

Closing the issue , based on the decision made in the issue https://github.com/openBackhaul/ExecutionAndTraceLog/issues/260