Version 2.0 (for use with SDL 2)

v2.0.0

Update install script, tags version 2

Version 1.0 (for use with SDL 1)

Merge pull request #154 from mitre/develop

Develop

v0.0.18

Changelog

Bug fix for sracp location handling.
Version number is now included in the printing of help for both sracp and fusera.

v0.0.17

bump version and tag

v0.0.16

Update install.sh

v0.0.15

Changelog

Fusera can now use a DBGaP cart, which means the accession field can be left blank!

Also internal code changes like:

1. Passing a Google instance token when on Google Cloud Platform in order to prove location to the SDL API.
2. Preparation for the acceptance of any type of DBGaP token: ngc, passport, or cart.

v0.0.14

Changelog

Manually setting the location to a cloud platform is a temporary thing as we build out fusera, so the ability to set the location to Google Cloud has been removed as a step towards removing it completely. This is because Fusera has the capability of resolving that it is running on the Google Cloud Platform as well as Amazon Web Services. This resolution is quite fast, so users should not be impacted.

This version of fusera also allows it to receive files from services that utilize FTP servers like ftp-ncbi.

Happy Thanksgiving!

v0.0.13

Changelog

This release comes with two new flags: silent and verbose. When fusera is ran without either of these flags, it acts in a more interactive manner with output meant to be read by its user. Silent should be utilized by scripts that only want fusera to fail or run, not to print any output. Finally, verbose should be used to generate output when troubleshooting and submitting an issue if the user thinks there is something wrong with fusera.

v0.0.12

Changelog

Added the ability to make requests to requester pays buckets and to allow users to specify which profile in their credentials file to use for requester pays.

v0.0.11

Changelog

Fusera no longer mounts when no accessions are successfully resolved with the SDL API. This prevents an "empty" fusera. Instead, fusera prints a message saying no accessions were successful and exits.

Fusera now limits calls to the API to 2k accessions, making multiple requests in succession to resolve more than 2k accessions for the user. This is in order to not burden the API, which would fail to resolve more than about 5k accessions at a time, resulting in an empty fusera.