-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feature: Implement subject endpoint to include ctTSOv2 analysis results from ICAv2 BYOB #684
Closed
1 task done
Comments
2 tasks
This is on me. Please kindly wait. I will need to think a bit on how best to tackle showing results (key files of interest) from the new pipeline (ctTSOv2) run in another system (ICAv2). This is not straight forward. |
sure, will update it when it is ready. |
victorskl
added a commit
to umccr/infrastructure
that referenced
this issue
Jun 14, 2024
… ctTSOv2 result * While building OrcaBus actively, we use current Portal to show ctTSOv2 output as new tab. * #434 * umccr/data-portal-apis#684 * Once new output path convention is stable, we can statically filter prefix only to subscribe cttsov2. * umccr/orcabus#350 * Related FileManager PR * umccr/orcabus#351
victorskl
changed the title
Feature: Add TSO V2 filter in the GDSFileManager for analysis results
Feature: Implement subject endpoint to include ctTSOv2 analysis results from ICAv2 BYOB
Jun 16, 2024
As discussed over Slack, taking over for API impl. |
victorskl
added a commit
that referenced
this issue
Jun 21, 2024
* Updated S3 event parser to handle ObjectCreated and ObjectDeleted come through EventBridge event envelope. * Added relevant unit test cases as guard-rail around parser logic * Part of story #684 * Related umccr/infrastructure#434
victorskl
added a commit
that referenced
this issue
Jul 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature
Add TSO V2 filter in the
GDSFileManagerICAv2 BYOB for analysis resultsTo Do
- [ ] the path format of tsov2 in the GDSFileManagerThe text was updated successfully, but these errors were encountered: