You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some kartons might want to know whether a karton task is originated from MWDB or not. This especially relevant for designs where samples arrive at Karton before they arrive in MWDB.
For example:
In order to prevent resubmitting of files again and again to sandboxes, we want our sandbox-dispatcher to check if the file was already analyzed, and if it does, don't submit it. It already works perfectly.
But we do have an issue, because we do want the file to be re-submitted to the sandboxes if a MWDB user pressed the REANALYZED karton button in MWDB. In this case, we want to force the system to resubmit the file to the sandboxes, even though it was analyzed before.
To do this, we need to find a way for sandbox-dispatcher to know if the file was sent by the integrated Karton in MWDB. This way we can check if the file came to the karton system from MWDB then submit it to sandboxes.
Describe the solution you'd like
Add some kind of persistence payload to the outgoing task, that indicates that the task was originated by mwdb.
Describe alternatives you've considered
More generic approach — add to karton a field named "original_source""original_origin""root_origin" or something like this, that will be assigned once, with the karton.identity of the karton that first produced this task.
Implement an API in karton that can be used like this get_origin_by_root_uid(task.root_uid) or something like root_ui.identity==karton.mwdb
The text was updated successfully, but these errors were encountered:
Feature Category
Describe the problem
Some kartons might want to know whether a karton task is originated from MWDB or not. This especially relevant for designs where samples arrive at Karton before they arrive in MWDB.
For example:
In order to prevent resubmitting of files again and again to sandboxes, we want our
sandbox-dispatcher
to check if the file was already analyzed, and if it does, don't submit it. It already works perfectly.But we do have an issue, because we do want the file to be re-submitted to the sandboxes if a MWDB user pressed the
REANALYZED
karton button in MWDB. In this case, we want to force the system to resubmit the file to the sandboxes, even though it was analyzed before.To do this, we need to find a way for
sandbox-dispatcher
to know if the file was sent by the integrated Karton in MWDB. This way we can checkif the file came to the karton system from MWDB then submit it to sandboxes
.Describe the solution you'd like
Add some kind of persistence payload to the outgoing task, that indicates that the task was originated by mwdb.
Describe alternatives you've considered
karton.identity
of the karton that first produced this task.get_origin_by_root_uid(task.root_uid)
or something likeroot_ui.identity==karton.mwdb
The text was updated successfully, but these errors were encountered: