fix: use v3 EDR management endpoints in Bruno collection#607
Open
yamisukii wants to merge 1 commit intoeclipse-edc:release/0.17.0from
Open
fix: use v3 EDR management endpoints in Bruno collection#607yamisukii wants to merge 1 commit intoeclipse-edc:release/0.17.0from
yamisukii wants to merge 1 commit intoeclipse-edc:release/0.17.0from
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR changes/adds
This fixes the EDR-related Bruno requests for the MVD
release/0.17.0flow.The Bruno collection currently uses the v4 management API for EDR endpoints:
/api/mgmt/v4/edrs/request/api/mgmt/v4/edrs/{transferProcessId}/dataaddressHowever, the EDR DataAddress endpoint is available under the v3 management API:
/api/mgmt/v3/edrs/{transferProcessId}/dataaddressThis PR updates the affected Bruno requests and README documentation accordingly.
Why it does that
In the current flow, the transfer process can reach
STARTEDsuccessfully and EDR metadata is stored in the consumer controlplane database, but the v4 EDR endpoint returns404 Not Found.Using the v3 EDR endpoint returns the expected DataAddress response.
Verified locally with Podman + KinD:
Who will sponsor this feature?
N/A - bug fix.
Linked Issue: Closes #604