Remove Balsamic QC

[Vince-janv]

Descripion

The workflow Balsamic QC has never and will probably never be used by customers. We are supporting it and maintaining logic for cases with this workflow set. Removing it would reduce the amount of logic we have to maintain.

User story

As a developer,
I want to remove the Balsamic QC workflow and all code tied to it,
So that we don't have to maintain unused code.

Work impact

Answer the following questions:

• How much time would be saved by implementing this feature on a weekly basis?
  • This would reduce development time in all projects dealing with the order flow
• How many users are affected by this issue?
  • All developers
• Are customers affected by this issue?
  • No customers are using this

Acceptance Criteria

• Customers can no longer place Balsamic QC orders
• All logic partaining to Balsamic QC is removed

Notes

• The order type should also be removed from the FE
• All 8 cases in the database with data_analysis='balsamic-qc' can be set to just 'balsamic'

[henrikstranneheim]

Remove QC code here: #3924

[henrikstranneheim]

Hermes: Clinical-Genomics/hermes#128

[henrikstranneheim]

Servers: https://github.com/Clinical-Genomics/servers/pull/1488

[diitaz93]

Initial technical refinement/ questions: Listing places where we would need to touch any code

• Balsamic QC is present in the following repositories (at least):

• cg

• Hermes

• Servers

• Trailblazer

• CiGRID

• clinical-genomics-ui

• Any other?? Arnold? Janus?

• How would this affect Scout?

• How would this affect gens?

• How would this affect locusDB?

• How would this affect Housekeeper? Is there a tag for balsamic-qc? What to do with files tagged with this?

We could start by removing BalsamicQC as an order option in the order portal, so that we don't get any more data

[diitaz93]

Side idea: Should we have a protocol for deprecating workflows? This can be a chance to create this protocol and documenting it