Releases: lilab-bcb/stratocumulus
Releases · lilab-bcb/stratocumulus
0.2.4
Fix sync
command for local backend (PR #26 by @yihming )
0.2.3
Feature improvement for cp command in local backend:
Automatically create parent folders if target is a directory. (PR #22 , #23 by @joshua-gould )
Support wildcard *. (PR #24 , #25 by @yihming )
0.2.1
- Add
-r
option back to strato cp
command for copying local folders to AWS S3 bucket. (PR #18 by @joshua-gould )
strato exists
command on AWS S3 folders now uses s3fs instead of boto3 package, in order to resolve the conflicts with pandas read_csv
function which are brought by later version of botocore package. (PR #17 by @joshua-gould ; PR #19 by @yihming )
0.2.0
Drop --backend
option and infer backend from the target URI. (Thanks to @joshua-gould in PR #13 )
0.1.7
Bug fix on AWS backend copy command with wildcards:
- Make such commands work for
subprocess.check_call
in the case when source paths are local. (PR #11 )
- Fix a bug for the case when source paths are relative with wildcards at top level, i.e.
*.txt
. (PR #12 )
0.1.5
- Bug fix for
cp
command with wildcards for AWS backend.
0.1.4
- Add
--profile
option for all commands:
- Works for
aws
backend only. Allow use AWS profile other than default. If not using this option, use the default profile.
- Add
--quiet
option for cp
, sync
, and rm
commands:
- If specified, Stratocumulus will not print the underlying AWS/GCP/Local commands on screen.
0.1.3
In cp
command:
- Copying multiple files using wildcards now works for AWS backend.
In exists
command:
- Make existence checking work for cloud folders in both GCP and AWS backend.
New command:
strato -v
or strato --version
to check the version of Stratocumulus.
0.1.2
Make behavior of strato sync
command consistent across backends.
0.1.1
- New feature:
- Add
--ionice
option for cp
and sync
commands, so that these operations can be run without monopolizing all the I/O bandwidth of local machines.