Communication between calling program and a launched run of manifest-based Ingestion process
As you can imagine, it is common practice for software vendors to offer UI-based insert/update/delete capability for meta data. Such program would have to interact with user (human) to gather information about a new Wellbore (for example) and then, behind the scene, make up JSON load/manifest to actually populate OSDU DP by creating a new Wellbore.
Ideally, such program needs to report back to the user (human) almost right away whether his/her effort (to create a new Wellbore in OSDU DP) has succeeded or not.
Not enough to tell the user “Here is the RunID, go and check status from Airflow console”.
Linked to #80
Perhaps a solution through Notification Service?
This also impacts EDS fetch-and-ingest workflow. cc - @jrougeau (for information)