changelog: Add entry for new handling of remote file inputs
@@ -5,6 +5,12 @@ We also use this change log to document new features that maintain backward comp
## New features since last version update
+ - 6 August 2021: We've replaced the mechanisms that support remote file inputs (e.g. `s3://` URLs) to improve internal workflow structure, extend support to `gs://`, `http://`, and `https://` URLs, and expand support for compressed inputs.
+ Our [remote file inputs documentation](docs/remote_inputs.md) is updated to reflect the changes.
+ This change should be backwards compatible and largely transparent to end users.
+ The most visible change for anyone using remote file inputs is the local download location of the remote files: instead of being within the `results/` directory, dynamic directories based on the remote URL are now used.
+ For example, the remote `metadata` input `https://data.nextstrain.org/files/ncov/open/metadata.tsv.gz` would be downloaded to the local path `data.nextstrain.org/files/ncov/open/metadata.tsv.gz`; the remote `sequences` input `s3://nextstrain-data/files/ncov/open/sequences.fasta.xz` would be downloaded to `nextstrain-data/files/ncov/open/sequences.fasta.xz`.
+
- 7 July 2021: Extensive changes to internally-used Nextstrain profiles.
There should be no breaking changes to existing workflows outside of `./nextstrain_profiles/`.
Please see [PR #628](https://github.com/nextstrain/ncov/pull/628) for full details. Briefly:
