Response To API Handling

[brothercorvo]

The integration manager currently utilizes a static RESPONSE action to construct the topic that is published across the integration manager upon the completion of a flow. This approach is problematic as it necessitates every DPService to subscribe to the same topic, leading to the indiscriminate distribution of all responses to all services.

Solutions

1. We could have services subscribe to every flow they use,
   • Advantages:
     • matches the current zmanager implementation
   • Disadvantages:
     • This limits the dynamic nature of digitalpy as we would need to define in advance every flow which could be called by a given service
2. We could change the integration manager so that if a flow is finished, it will publish the topic with the service_id as the config
   • Advantages:
     • Simple to implement with integration manager and service
     • Flexible
     • Fewer topics required
   • Disadvantages:
     • Uses the config in a potentially unexpected way