Request to add description of call backs that ends subscription of old release, if new-application is of same release and same application name for /v1/bequeath-your-data-and-die service

[vanithavalluripalli9]

Problem Description:

Scenario : Same Release of application but deployed in different address and port.

When a same release but deployed in different address and port of existing application is registered , it will update the http-c , tcp-c of old Release in config file of New application with the preceding application information provided in request body.

Once the application is approved and receives “embed-yourself” , a callback will be triggered to the old application’s “/v1/bequeath-your-data-and-die” .

When /v1/bequeath-your-data-and-die is executed,it will update the NewRelease http-c,tcp-c with the new application details.

Then during series of call backs following callbacks should not be sent

PromptForBequeathingDataCausesRObeingRequestedToStopNotificationsToOldRelease promptForBequeathingDataCausesRequestForDeregisteringOfOldRelease As, it will lead to end of subscriptions of same application .

Solution:

To add description for callbacks mentioned below :

• PromptForBequeathingDataCausesRObeingRequestedToStopNotificationsToOldRelease
• promptForBequeathingDataCausesRequestForDeregisteringOfOldRelease

As ,

Call back will not be sent, if new-application-name == application name in -http-s-000 and new-application-address == address in -http-s-000

[vanithavalluripalli9]

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