search

umccr / nextflow-stack

AWS stack to run Nextflow pipelines on Batch using shared resources
0 stars 0 forks source link

Add cost allocation tags and propagate the tags #86

Closed brainstorm closed 8 months ago

brainstorm commented 8 months ago

Fixes #85

@scwatts Please deploy/test, I'm not breaking your pipes accidentally ;)

@reisingerf Would you add the SubStack key to better track which sub-pipeline is costing? I see there's other pipes such as sash, etc... but I'm not sure if there's a establish those accordingly?

reisingerf commented 8 months ago

Would you want to add a execution specific tag (i.e. portal_run_id based) while at it?

brainstorm commented 8 months ago

Would you want to add a execution specific tag (i.e. portal_run_id based) while at it?

That! I knew I was missing something XD

reisingerf commented 8 months ago

And a minor one for @scwatts : do we want to rename this stack to something more customised/specific to OA rather than generic Nextflow?

scwatts commented 8 months ago

Sorry, got caught up today - LGTM thanks Roman!

I think having the generic 'NextflowStack' name is okay since we might end up running WISP etc here over the next couple of months.

One minor request, can we either change the 'SubStack' values to match pipeline names here or just have oncoanalyser shown as 'Oncoanalyser'?