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

fix(DataPlane): Add system test for Client Data Pull with query parameters in the request #1731

Conversation

bscholtes1A
Copy link
Contributor

@bscholtes1A bscholtes1A commented Jul 22, 2022

What this PR changes/adds

This PR adds a system test covering the use-case of a client data pull (see #585 for more details) with query parameters passed in input of the Data Plane public API.

Why it does that

Ensure query parameters are properly conveyed all the way to the provider data source (if its allows it).

Linked Issue(s)

Closes #1180

Checklist

  • added appropriate tests?
  • performed checkstyle check locally?
  • added/updated copyright headers?
  • documented public classes/methods?
  • added/updated relevant documentation?
  • added relevant details to the changelog? (skip with label no-changelog)
  • formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

@bscholtes1A bscholtes1A marked this pull request as draft July 22, 2022 14:37
@bscholtes1A bscholtes1A force-pushed the 1180-integration_test_data_plane_proxy_filtering branch from 938a500 to 54924de Compare July 22, 2022 14:59
@bscholtes1A bscholtes1A changed the title fix(DataPlane): Add integration test covering the case where Request parameters are p… fix(DataPlane): Add system test for Client Data Pull with query parameters in the request Jul 22, 2022
@bscholtes1A bscholtes1A force-pushed the 1180-integration_test_data_plane_proxy_filtering branch 4 times, most recently from 6052142 to 5350a08 Compare July 25, 2022 07:12
.as(EndpointDataReference.class);

// pull the data
await().atMost(timeout).untilAsserted(() -> given()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe also this part could be included in the same method I proposed above: the method on participant could be like getData or pullData and it could hide all the edr details

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated, could you please have another look?

@bscholtes1A bscholtes1A force-pushed the 1180-integration_test_data_plane_proxy_filtering branch from 5350a08 to a5eaa4e Compare July 25, 2022 07:48
@bscholtes1A bscholtes1A marked this pull request as ready for review July 25, 2022 07:49
@ndr-brt ndr-brt self-requested a review July 25, 2022 10:21
…rovided when querying the Data Plane public API
@bscholtes1A bscholtes1A force-pushed the 1180-integration_test_data_plane_proxy_filtering branch from a5eaa4e to e7e189c Compare July 25, 2022 10:31
@bscholtes1A bscholtes1A merged commit 5f7729c into eclipse-edc:main Jul 25, 2022
diegogomez-zf pushed a commit to diegogomez-zf/DataSpaceConnector that referenced this pull request Aug 3, 2022
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.

Data Plane consumer proxy filters request properties
2 participants