Skip to content
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

Replace backported provisioners with upstream module #1538

Open
paullatzelsperger opened this issue Sep 6, 2024 · 1 comment
Open

Replace backported provisioners with upstream module #1538

paullatzelsperger opened this issue Sep 6, 2024 · 1 comment
Labels
enhancement New feature or request Feature

Comments

@paullatzelsperger
Copy link
Contributor

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.

@paullatzelsperger paullatzelsperger added enhancement New feature or request Feature labels Sep 6, 2024
Copy link
Contributor

This issue is stale because it has been open for 2 weeks with no activity.

@github-actions github-actions bot added the stale label Sep 21, 2024
@ndr-brt ndr-brt removed the stale label Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Feature
Projects
Status: Open
Development

No branches or pull requests

2 participants