-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs: Blob transfer Architectural Decision Record #233
Docs: Blob transfer Architectural Decision Record #233
Conversation
Unit Test Results 386 files - 6 386 suites - 6 8m 42s ⏱️ - 9m 43s For more details on these failures, see this check. Results for commit 6f41446. ± Comparison against base commit 6065693. ♻️ This comment has been updated with latest results. |
docs/developer/decision-records/2022-04-21-dpf-blob-data-transfer/README.md
Outdated
Show resolved
Hide resolved
…fer/README.md Co-authored-by: Izabela Kulakowska <[email protected]>
docs/developer/decision-records/2022-04-21-dpf-blob-data-transfer/README.md
Outdated
Show resolved
Hide resolved
…aSpaceConnector into docs/231-blob-transfer-adr
Codecov Report
@@ Coverage Diff @@
## docs/1183-blob-transfer-adr #233 +/- ##
==============================================================
Coverage 58.61% 58.61%
Complexity 2731 2731
==============================================================
Files 698 698
Lines 15444 15444
Branches 1045 1045
==============================================================
Hits 9053 9053
Misses 5967 5967
Partials 424 424 Continue to review full report at Codecov.
|
…aSpaceConnector into docs/231-blob-transfer-adr
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
resolved open comment
12 and 13 (now 13 and 14) should be separate loops, these are not synchronised |
in (16) "deletes the container containing the blob and the SAS token" the token is not in the container. We should add an arrow (17) whereby the consumer deletes the Sas token in its vault. |
nit: it would make the puml clearer to have service activation boxes across 2/3/4/13 for Consumer, across 5/6 for Provider and across 6/7/8/9/10/11 for DPF and across 14/15 for Client, across 15/16/(new)17 for Consumer |
Pushed some proofreading fixes |
* Docs: Blob transfer Architectural Decision Record (#233) Added Azure blob transfer Architectural Decision Record. * Updated changelog. * Fixed PR number in changelog. * Applied suggestion. Co-authored-by: Paul Latzelsperger <[email protected]> * Applied suggestions. Co-authored-by: Paul Latzelsperger <[email protected]> * Update docs/developer/decision-records/2022-04-21-dpf-blob-data-transfer/README.md Co-authored-by: Paul Latzelsperger <[email protected]> * Update docs/developer/decision-records/2022-04-21-dpf-blob-data-transfer/README.md Co-authored-by: Paul Latzelsperger <[email protected]> * Update docs/developer/decision-records/2022-04-21-dpf-blob-data-transfer/README.md Co-authored-by: Paul Latzelsperger <[email protected]> * Moved client poll. * Update docs/developer/decision-records/2022-04-21-dpf-blob-data-transfer/README.md Co-authored-by: Paul Latzelsperger <[email protected]> * Made 17 and 18 substep of 16. Co-authored-by: Paul Latzelsperger <[email protected]>
The goal of this document is to explain what should be implemented. This document does not represents what is already implemented.
For example, right now DPF uses the storage account key (SHARED_KEY), but the SAS token is not used yet (not written and read from Vault).