Skip to content
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

Create TES Basespace Upload manager service #186

Merged
merged 16 commits into from
Apr 22, 2024

Conversation

alexiswl
Copy link
Member

@alexiswl alexiswl commented Mar 25, 2024

TODO

  • Instead of using portal token secret, get authentication from sscheck service another way
  • Add event rule to collect SRM PendingAnalysis event to trigger step functions
  • Add stack to OrcaBus pipeline
  • Determine if BSSH Secret should be part of this stack or part of infrastructure stack? (This should only be a temp stack anyway)

@alexiswl alexiswl added the feature New feature label Mar 25, 2024
@alexiswl alexiswl requested a review from victorskl March 25, 2024 04:06
@alexiswl alexiswl self-assigned this Mar 25, 2024
@alexiswl alexiswl marked this pull request as draft March 25, 2024 04:06
@alexiswl alexiswl linked an issue Mar 25, 2024 that may be closed by this pull request
@victorskl
Copy link
Member

Made a quick go through, looking good. Will go through full review once ready.

@alexiswl alexiswl force-pushed the feature/tes-bs-runs-upload-manager branch from eb1be50 to 5e13dd4 Compare April 17, 2024 08:52
@alexiswl alexiswl marked this pull request as ready for review April 17, 2024 08:52
@alexiswl
Copy link
Member Author

@victorskl would you mind triggering a srm sequencestatechange in dev and seeing if that triggers this AWS Step function?

Might need to be more specific on the filter too (so just to when the statechange is pending analysis?).

I would expect the dev step function to fail because it might not be able to generate the v2 samplesheet but just want to make sure that the events are talking.

I have deployed stack manually in dev but also added to orcabus pipeline. Will destroy manual dev stack before merging.

@victorskl
Copy link
Member

will do

@alexiswl
Copy link
Member Author

Gah @williamputraintan is #231 the last of the refactoring?

@victorskl
Copy link
Member

Gah

(I knew it.! Hang in there, Alexis)

@williamputraintan
Copy link
Member

#231 the last of the refactoring?

Yes, no more refactoring!

@victorskl
Copy link
Member

Will; let pause the refactor activity at this point. I reckon, we really achieved pretty good refactor this far (thank you, again). We shall let it sit the current code base (what we got up to main this far) as it is for a bit more. We shall later go more rounds refactor later down the track, again.

@alexiswl alexiswl force-pushed the feature/tes-bs-runs-upload-manager branch from 5e13dd4 to 143d38b Compare April 18, 2024 02:37
Copy link
Member

@victorskl victorskl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good, Alexis. Minor comments to attend.

@alexiswl alexiswl force-pushed the feature/tes-bs-runs-upload-manager branch from fcf9326 to a3cc3e4 Compare April 18, 2024 10:42
alexiswl and others added 8 commits April 22, 2024 11:14
Filtered event and updated step function inputs to match sequence.

Ran `yarn run prettier --write` to update linting for ts files
…us only

Updated orcabus pipeline stack collection class
Import path fixes after refactor

Deleted blank deployment readme
@alexiswl alexiswl force-pushed the feature/tes-bs-runs-upload-manager branch from 583507c to d5ec8db Compare April 22, 2024 01:23
ESLint ignore for beforeBinding command
Run prettier --write for bssh tools lambda layer
@alexiswl
Copy link
Member Author

@victorskl do you want to look over this again, have refactored onto main and cdk synth now working

@victorskl
Copy link
Member

Go for it, Alexis. Pls merge whenever you feel ready. These are all moving targets. We can readjust down the track. Let us pushing forwards...

@alexiswl
Copy link
Member Author

Woo hoo! One down, five PRs to go

@alexiswl alexiswl merged commit 11f77d3 into main Apr 22, 2024
2 checks passed
@alexiswl alexiswl deleted the feature/tes-bs-runs-upload-manager branch April 22, 2024 01:59
@victorskl
Copy link
Member

five PRs to go

You should rest and enjoy ur holis...

I can/will follow up testing this part meanwhile.

Once we got this part up and running, we should get to fastqs - that is pretty good, already.!

Thanks for all hard work.!

constructor(scope: Construct, id: string, props: PythonLambdaLayerConstructProps) {
super(scope, id);

this.lambda_layer_version_obj = new PythonLayerVersion(this, 'python_lambda_layer', {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alexiswl Just minor request, pls.

I just notice these as post-mortem review. When you have spare time down the track, could you please follow up refactoring naming convention on these CDK variables. There seems to be mixed use of snake_case and camelCase.

ditto - current guidance on TypeScript
https://github.com/umccr/orcabus/blob/main/README.md#typography

This apply to both bsRunsUploadManager and ICAv2CopyBatchManager services that have merged.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And.. separate PRs for these refactor, pls.

Copy link
Member Author

@alexiswl alexiswl Apr 29, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And.. separate PRs for these refactor, pls.

Ah that's going to cause some annoying merge conflicts, the PythonLayer construct example above will rename the attribute lambda_layer_version_obj to lambdaLayerVersionObj, but the property of the bs runs upload manager stack (lambda_layer_obj will be renamed to lambdaLayerObj),

so the layers attribute in any of the python functions will go from layers: [props.lambda_layer_obj.lambda_layer_version_obj] to layers: [props.lambdaLayerObj.lambdaLayerVersionObj] where lambdaLayerObj comes from one branch and lambdaLayerVersionObj comes from another branch.

I think this would be easier to all be in one PR

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, sure. In that case, that's fine, Alexis. Thanks

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean, ok to be all in one go, refactor PR, yes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement sequence run data copy service
3 participants