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
Provisioner modules (Azure Blob,...) were backported (=copied) into the Tx-EDC code base.
Once Tx-EDC has been upgraded to the latest version of the upstream EDC (0.10.0-SNAPSHOT at time of writing), the backported module(s) should be removed again and replaced with upstream modules.
Backported modules are located in edc-extensions/backport.
Note that the Azure- and S3 cloud tests will need to be adapted, because they still use the old control API and must be upgraded to use the Signaling API!
WHY
avoid technical debt and diverging code streams
HOW
bump EDC, delete the backported modules, replace with upstream variants
WHAT
Provisioner modules (Azure Blob,...) were backported (=copied) into the Tx-EDC code base.
Once Tx-EDC has been upgraded to the latest version of the upstream EDC (0.10.0-SNAPSHOT at time of writing), the backported module(s) should be removed again and replaced with upstream modules.
Backported modules are located in
edc-extensions/backport
.Note that the Azure- and S3 cloud tests will need to be adapted, because they still use the old control API and must be upgraded to use the Signaling API!
WHY
avoid technical debt and diverging code streams
HOW
bump EDC, delete the backported modules, replace with upstream variants
FURTHER NOTES
// anything else you want to outline
Please be sure to take a look at
our contribution guidelines and
our PR etiquette.
The text was updated successfully, but these errors were encountered: