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.

Sign up for GitHub

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: add missing edc-control-plane-api-client dependency (#134) #138

Merged
merged 1 commit into from
Oct 20, 2023
Merged

fix: add missing edc-control-plane-api-client dependency (#134) #138

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions transfer/transfer-07-provider-push-http/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
# Implement a simple "Provider Push" Http transfer flow

The purpose of this example is to show a data exchange between 2 connectors, one representing the
data provider and the other, the consumer. It's based on a provider push usecase that you can find
The purpose of this example is to show a data exchange between two connectors, one representing the
data provider and the other, the consumer. It's based on a provider push use case that you can find
more details
on [Transfer data plane documentation](https://github.com/eclipse-edc/Connector/tree/main/extensions/control-plane/transfer/transfer-data-plane)
on [Transfer data plane documentation](https://github.com/eclipse-edc/Connector/tree/main/extensions/control-plane/transfer/transfer-data-plane).
For the sake of simplicity, the provider and the consumer
will be on the same machine, but in a real world configuration, they will likely be on different
machines. The final goal of this example is to present the steps through which the 2 connectors will
machines. The final goal of this example is to present the steps through which the two connectors will
have to pass so that the consumer can have access to the data, held by the provider.

Those steps are the following:
Expand Down Expand Up @@ -297,7 +297,7 @@ looks as follows:
reference

Of course, this is the simplest possible negotiation sequence. Later on, both connectors can also
send counter offers in addition to just confirming or declining an offer.
send counteroffers in addition to just confirming or declining an offer.

```bash
curl -d '{
Expand Down
1 change: 1 addition & 0 deletions transfer/transfer-07-provider-push-http/http-push-connector/build.gradle.kts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@ repositories {

dependencies {
implementation(libs.edc.control.plane.core)
implementation(libs.edc.control.plane.api.client)
implementation(libs.edc.dsp)
implementation(libs.edc.configuration.filesystem)
implementation(libs.edc.vault.filesystem)
Expand Down