Using bazel's download machinery, download (for files) and download_and_extract (for archives), has three main benefits:
- it's fairly reliable --
aws s3 cp is generally disappointing + seems to get worse in large repos -- may get better pooling with bazel involved
- gives access to bazel's repository_cache (I'm not sure if this is exposed outside of these APIs)
- de-duplicate extraction logic
some tools, for example the aws cli, can generate a presigned url which can in turn be given to bazel to download. This allows direct downloads with bazel for private artifacts using standard AWS credentials.
Using bazel's download machinery,
download(for files) anddownload_and_extract(for archives), has three main benefits:aws s3 cpis generally disappointing + seems to get worse in large repos -- may get better pooling with bazel involvedsome tools, for example the aws cli, can generate a presigned url which can in turn be given to bazel to download. This allows direct downloads with bazel for private artifacts using standard AWS credentials.