Munish Chouhan

@pabloaledo I have used the master branch of nextflow but still got the same error

@pditommaso SubmitContainerTokenRequest in Tower doesn't have WorkflowId in it should i add it there? https://github.com/seqeralabs/nf-tower-cloud/blob/14a5582fe2aa84b5fda9706e3f6776d9084ced8c/tower-enterprise/src/main/groovy/io/seqera/wave/SubmitContainerTokenRequest.groovy#L32-L79

ok i will make the changes in tower

Found the issue The parameter name was different in Wave-API and Nextflow should we use wave-api in nextflow and tower for wave models so that it remains consistent? Created new...

I have tested using local compute, got this ` INFO i.s.w.service.CredentialServiceImpl - ------Found compute env: local-platform and credentials: null` I will test with aws-batch next

pipeline with aws-batch is not running properly in local I will try some alternative

I have tested this PR with local-platform after correcting the credentialsId type for sanity check I got this, which ``` 16:10:21.174 [io-executor-thread-2] INFO i.s.w.service.CredentialServiceImpl - Platform = local-platform and credentials.id...

@pditommaso I tried testing this PR in local with AWS Batch, but it doesn't work can we test this in stage or dev?

> @munishchouhan Any chance to fix failing tests at your convenience ? sure

Tested Blob Transfer: Successful ``` % wave -i cr.seqera.io/public/nf-jdk:corretto-17-al2023-jemalloc --wave-endpoint https://wave.stage-seqera.io wave.stage-seqera.io/wt/XXXXX/public/nf-jdk:corretto-17-al2023-jemalloc (base) munish.chouhan@Munishs-MacBook-Pro ~ % docker pull wave.stage-seqera.io/wt/XXXXX/public/nf-jdk:corretto-17-al2023-jemalloc corretto-17-al2023-jemalloc: Pulling from wt/XXXXXX/public/nf-jdk 860904071dc6: Pull complete 82160a56be4d: Pull complete d2d64551932e:...