search

DataBiosphere / ssds

Simple data storage system for AWS and GCP
MIT License
2 stars 1 forks source link

Introduce data "release" #213

Closed xbrianh closed 4 years ago

xbrianh commented 4 years ago

This copies data from a submission into "release" areas, as defined by a user provided transfer CSV file. Destination keys must being with the prefix "working", but are otherwise unrestricted.

A versioned manifest of the release transfer is saved in the submission source bucket under the key: release-transfer-manifests/{submission_id}/transfer.{version}, where "version" is a formatted datetime, e.g. "2020-10-26T192530.137917Z"

When using the CLI, releases occur in a single deployment of the SSDS. This means that objects are copied to a different location of the same bucket. The Python API can be used to release objects to separate SSDS deployments.

depends on #212

codecov-io commented 4 years ago

Codecov Report

Merging #213 into dev will increase coverage by 0.06%. The diff coverage is 82.97%.

Impacted file tree graph

@@            Coverage Diff             @@
##              dev     #213      +/-   ##
==========================================
+ Coverage   86.63%   86.70%   +0.06%     
==========================================
  Files          16       16              
  Lines        1025     1068      +43     
==========================================
+ Hits          888      926      +38     
- Misses        137      142       +5
Impacted Files Coverage Δ
ssds/cli/staging.py 66.66% <20.00%> (-8.85%) :arrow_down:
ssds/__init__.py 89.93% <100.00%> (+3.09%) :arrow_up:
ssds/storage.py 94.51% <0.00%> (+1.21%) :arrow_up:

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 bd8f6fd...0f3c415. Read the comment docs.