You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
End-to-end flow for managing configuration and credentials for blob storage transfers is not working. Integration tests exist in the separate layers, but the end-to-end flow is not functional. One issue is that there are two classes named AzureBlobStoreSchema with different properties inside (#235).
While investigating the problem, it also appeared that documentation to understand how the system should work is missing.
How the managedResources attribute is used
What kinds of keys are used/transferred (shared access key vs. short-lived SAS)
How vaults are used
AzureStorageDataSourceFactory should call vault.getSecret(dataAddress.getKeyName()) instead of dataAddress.getProperty(AzureBlobStoreSchema.SHARED_KEY))
Acceptance Criteria
ADR to describe blob transfer end-to-end flow approach and details.
End-to-end test to verify blob data transfer (managedResources=true).
Test runs as part of CI.
Update docs.
Tasks
ADR on blob transfer end-to-end flow.
Add new end-to-end test to verify blob data transfer using DataManagement APIs
Upstream eclipse-edc#1183
After #235, #236
Description
End-to-end flow for managing configuration and credentials for blob storage transfers is not working. Integration tests exist in the separate layers, but the end-to-end flow is not functional. One issue is that there are two classes named AzureBlobStoreSchema with different properties inside (#235).
While investigating the problem, it also appeared that documentation to understand how the system should work is missing.
managedResources
attribute is usedAzureStorageDataSourceFactory should call
vault.getSecret(dataAddress.getKeyName())
instead ofdataAddress.getProperty(AzureBlobStoreSchema.SHARED_KEY))
Acceptance Criteria
Tasks
The text was updated successfully, but these errors were encountered: