-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delete old flow cell before adding re-demultiplexed flow cell #2593
Conversation
Nice! Seems to already have support for filtering on the flow cell tag! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. We should check with @karlnyr if this is the behaviour that we want in CG (i.e. deleting previous flow cell entries)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like having the delete call here rather than before demultiplexing.
Here are some thoughts though:
- Simplify
delete_demux_api.delete_flow_cell
to only perform what we think is useful - Since the call is moved after demultiplexing, it should not remove any directories.
- It should not remove the sample sheet
- Do we need to check active samples? (more hassle than worth)
Wait for input from prod. This function is also called in the CLI command
so
This one is hard, we will have to decouple the sample sheet and Housekeeper deletion if I understand correctly
I guess this is for when you want to delete the metrics but not the flow cell?
We do check active samples when we call |
… into delete-flowcell-post-processing
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
# Conflicts: # cg/meta/demultiplex/housekeeper_storage_functions.py # cg/meta/demultiplex/status_db_storage_functions.py
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like the structure of the new delete functions. I am a bit concerned about the order of the commands store_flow_cell_data
and delete_flow_cell_data
in finish_flow_cell
. Also, I am thinking if it would be useful to leave the CLI command for testing purposes, specially when testing the demultiplex process without invoking the finish command
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool beans 🔥
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clip it and ship it. Time for vacation 🌴
Finishing from scratch (flow cell not added previously) also worked |
Deployed in stage and production |
Description
Part of the tasks in #2541.
In #2144 the automatic deletion of a flow cell from Housekeeper and StatusDB was removed, having to explicitly delete a flow cell before re-demultiplexing.
This PR re-adds the functionality in a slightly different way.
Changed
Delete_flow_cell_API
cg demultiplex delete-flow-cell
CLI commandBefore post-processing:
How to prepare for test
us
paxa
How to test
cg demultiplex finish flow-cell 230908_A01901_0231_BHJWJFDSX7
Expected test outcome
Review
Thanks for filling in who performed the code review and the test!
This version is a
Implementation Plan