Skip to content

fix: use v3 EDR management endpoints in Bruno collection#607

Open
yamisukii wants to merge 1 commit intoeclipse-edc:release/0.17.0from
yamisukii:fix/edr-management-api-v3
Open

fix: use v3 EDR management endpoints in Bruno collection#607
yamisukii wants to merge 1 commit intoeclipse-edc:release/0.17.0from
yamisukii:fix/edr-management-api-v3

Conversation

@yamisukii
Copy link
Copy Markdown

@yamisukii yamisukii commented Apr 27, 2026

What this PR changes/adds

This fixes the EDR-related Bruno requests for the MVD release/0.17.0 flow.

The Bruno collection currently uses the v4 management API for EDR endpoints:

  • /api/mgmt/v4/edrs/request
  • /api/mgmt/v4/edrs/{transferProcessId}/dataaddress

However, the EDR DataAddress endpoint is available under the v3 management API:

  • /api/mgmt/v3/edrs/{transferProcessId}/dataaddress

This PR updates the affected Bruno requests and README documentation accordingly.

Why it does that

In the current flow, the transfer process can reach STARTED successfully and EDR metadata is stored in the consumer controlplane database, but the v4 EDR endpoint returns 404 Not Found.

Using the v3 EDR endpoint returns the expected DataAddress response.

Verified locally with Podman + KinD:

curl -i -X GET "http://127.0.0.1/api/mgmt/v3/edrs/<transferProcessId>/dataaddress" \
  -H "Host: cp.consumer.localhost" \
  -H "X-Api-Key: password"

Who will sponsor this feature?

N/A - bug fix.

Linked Issue: Closes #604

@yamisukii yamisukii requested a review from a team as a code owner April 27, 2026 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant