Biocontainer api

[KevinMenden]

Use the Biocontainers API instead of quay.io to get container tags for Docker and Singularity containers as suggested in #875

I have not implemented any questionary selection now, as you have suggested @ewels . Mainly because I think it would be good to have the most recent version as default, and allowing users to choose a container tag/version for both Docker and Singularity could mean they choose different builds. The linter should complain about this, or we could directly check within nf-core modules create, but easiest would be to just avoid this in the first place.

Wouldn't be too hard to add it in though so up for discussion I'd say :-)

PR checklist

• This comment contains a description of changes (with reason)
• CHANGELOG.md is updated
• If you've fixed a bug or added code that should be tested, add tests!
• Documentation in docs is updated

[codecov]

Codecov Report

Merging #1110 (3de0710) into dev (f18560d) will increase coverage by 0.07%.
The diff coverage is 81.48%.

@@            Coverage Diff             @@
##              dev    #1110      +/-   ##
==========================================
+ Coverage   72.31%   72.38%   +0.07%     
==========================================
  Files          36       36              
  Lines        4547     4552       +5     
==========================================
+ Hits         3288     3295       +7     
+ Misses       1259     1257       -2     

Impacted Files	Coverage Δ
nf_core/modules/create.py	78.01% <71.42%> (+0.23%)	⬆️
nf_core/utils.py	83.83% <85.00%> (+0.68%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f18560d...3de0710. Read the comment docs.

[ewels]

Haven't tested it, but general code read-over looks good!

[ErikDanielsson]

Looks good! Just found a few minor things.

[ErikDanielsson]

Are we guaranteed by the API to at least get both one Docker and Singularity image tag? Since this might raise an error otherwise.

[KevinMenden]

I think if there the response is successful, then in theory, there should be at least one of both. And if one of them stays None then that's actually okay for the template. But yeah might be worth trying this out a little bit and make it a bit robuster ....

[KevinMenden]

Yes it should be fine, it either raises an error, returns the images or None, and None can be handled by nf-core modules create (will just print YOUR-TOOL-HERE in the main.nf file instead)