Bug report

Expected behavior and actual behavior

When passing an s3 path for the -params-file parameter, I'd expect nextflow to use nf-amazon plugin to get it. This works with version 25.04.8 but not in 25.10.0 anymore.

Steps to reproduce the problem

nextflow run https://github.com/seqeralabs/nf-hello-world -params-file s3://example_bucket/hello/params.json

Program output

 N E X T F L O W   ~  version 25.10.0

WARN: Unable to start plugin 'nf-amazon' required by s3://example_bucket/hello/params.json
ERROR ~ Missing plugin 'nf-amazon' required to read file: s3://example_bucket/hello/params.json

 -- Check '.nextflow.log' file for details

I get the same error even if I use an actual s3 path so the path itself doesn't matter....

Environment

• Nextflow version: 25.10.0
• Java version: openjdk version "17.0.6" 2023-01-17 LTS
• Operating system: macOS
• Bash version: zsh 5.9 (arm64-apple-darwin24.0)

Additional context

If I downgrade to nextflow version 25.04.8 then it works correctly (with the above command it then complains that the s3 path doesn't exist but thats a valid error)