From 20bf3fa475b52ccc9b975340b4119b0ecaf09f55 Mon Sep 17 00:00:00 2001 From: Tomvbe <34196062+Tomvbe@users.noreply.github.com> Date: Tue, 9 Jan 2024 15:53:08 +0100 Subject: [PATCH] chore: move e2e to own repo (#6) * chore: move e2e to own repo * Fix branch --- README.MD | 5 +- e2e-test/README.md | 658 ------------------ e2e-test/certs/cert.pem | 21 - e2e-test/certs/cert.pfx | Bin 2477 -> 0 bytes e2e-test/certs/key.pem | 28 - e2e-test/config/devices.paged.ttl | 8 - e2e-test/config/devices.ttl | 10 - e2e-test/config/ldes-server.config.yml | 19 - e2e-test/config/seed.sh | 14 - e2e-test/data/device.template.json | 109 --- e2e-test/docker-compose.yml | 157 ----- .../catalog-configuration.properties | 6 - e2e-test/federated-catalog/nodes-dc.json | 9 - .../consumer-configuration.properties | 18 - .../consumer-vault.properties | 1 - .../provider-configuration.properties | 18 - .../provider-vault.properties | 1 - e2e-test/ldio-config.yml | 19 - e2e-test/ldio-server-seeder.yml | 23 - 19 files changed, 4 insertions(+), 1120 deletions(-) delete mode 100644 e2e-test/README.md delete mode 100644 e2e-test/certs/cert.pem delete mode 100644 e2e-test/certs/cert.pfx delete mode 100644 e2e-test/certs/key.pem delete mode 100644 e2e-test/config/devices.paged.ttl delete mode 100644 e2e-test/config/devices.ttl delete mode 100644 e2e-test/config/ldes-server.config.yml delete mode 100755 e2e-test/config/seed.sh delete mode 100644 e2e-test/data/device.template.json delete mode 100644 e2e-test/docker-compose.yml delete mode 100644 e2e-test/federated-catalog/catalog-configuration.properties delete mode 100644 e2e-test/federated-catalog/nodes-dc.json delete mode 100644 e2e-test/http-pull-consumer/consumer-configuration.properties delete mode 100644 e2e-test/http-pull-consumer/consumer-vault.properties delete mode 100644 e2e-test/http-pull-provider/provider-configuration.properties delete mode 100644 e2e-test/http-pull-provider/provider-vault.properties delete mode 100644 e2e-test/ldio-config.yml delete mode 100644 e2e-test/ldio-server-seeder.yml diff --git a/README.MD b/README.MD index 9122379..8703cf8 100644 --- a/README.MD +++ b/README.MD @@ -14,7 +14,10 @@ To create the images run the following docker commands from the root directory: docker build -t vsds-federated-catalog-connector:local . -f ./federated-catalog-connector/Dockerfile ``` -> **Note**: These connectors are not production ready and should only be used for development purposes. + > **Note**: These connectors are not production ready and should only be used for development purposes. + +3. E2E testing + - [Basic flow](https://github.com/Informatievlaanderen/VSDS-LDES-E2E-testing/tree/main/tests/034.dataspace-connector-consumer-and-provider) ## Next steps: diff --git a/e2e-test/README.md b/e2e-test/README.md deleted file mode 100644 index 842f4f0..0000000 --- a/e2e-test/README.md +++ /dev/null @@ -1,658 +0,0 @@ -# Implement a simple flow from LdesClient to LdesServer with EDC Connectors. - -This example is based on [transfer-06-consumer-pull-http](https://github.com/eclipse-edc/Samples/tree/main/transfer/transfer-06-consumer-pull-http). - -The purpose of this example is to show a data exchange between 2 connectors, one representing the -data provider (LDES Server) and the other, the consumer (LDES Client). It's based on a consumer pull usecase 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) -The provider and the consumer will run in two different containers of the same connector image. -The final goal of this example is to present the steps through which the 2 connectors will -have to pass so that the consumer can have access to the data, held by the provider. - -Those steps are the following: - -* Prepare the LDES Server -* Running the provider connector -* Running the consumer connector -* Running a Http server that will receive the Endpoint Data Reference on the consumer side, that - contains the url to be used to get the data. -* Register data plane instance for provider connector -* Register data plane instance for consumer connector -* Create an Asset on the provider (The asset will be the data to be shared) -* Create an access policy on the provider (The policy will define the access right to the data) -* Create a contract definition on the provider - -At this step, the consumer should be able to fetch the catalog from the provider and to see the -contract offer generated from the resources that have been created. - -Once the catalog is available, to access the data, the consumer should follow the following steps: - -* Performing a contract negotiation with the provider -* Performing a transfer - * The consumer will initiate a file transfer - * The provider will send an EndpointDataReference to the consumer -* The consumer could reach the endpoint and access the data - - -> For the sake of simplicity, we will use an in-memory catalog and fill it with just one single -> asset. This will be deleted after the provider shutdown. - -# Server setup - -To prepare the LDES Server we use the following containers: -- ldes-server: The actual server. -- test-message-generator: Generates messages to seed the server with data. -- ldio-server-seeder: ETL pipeline between the message generator and the server to insert the generated data into the server. -- ldes-mongodb: Data persistence used by the server. - -Start the LDES Server: - -```bash -docker compose up -d -``` - -Please ensure that the LDES Server is ready to ingest by following the container log until you see the following message `Cancelled mongock lock daemon`: -```bash -docker logs --tail 1000 -f $(docker ps -q --filter "name=ldes-server$") -``` -Press `CTRL-C` to stop following the log. - -> **Note**: as of server v1.0 which uses dynamic configuration you need to execute the [seed script](./config/seed.sh) to setup the LDES with its views: -```bash -chmod +x ./config/seed.sh -sh ./config/seed.sh -``` - -Seed the LDES Server by starting the message generator: - ```bash - docker compose up test-message-generator -d - ``` - -Verify that messages are correctly ingested by the server: -```bash -curl http://localhost:8081/devices/paged?pageNumber=1 -``` - -### Provider connector - -The provider connector is the one providing EndpointDataReference to the consumer after it initiates -a transfer. - -### Consumer connector - -The consumer is the one "requesting" the data to the provider. - -# How to run a connector - -In fact, in the configuration of our example, both the provider and the consumer are connectors. -Therefore, to set up our example, we need to start a connector with the configuration for a provider -and another one with the configuration of a consumer. - -It is important to note that only the property file differs between the consumer and the provider. -You can find the configuration file in the directories below: - -* [provider](http-pull-provider/provider-configuration.properties) -* [consumer](http-pull-consumer/consumer-configuration.properties) - -The section bellow will show you some explanation about some of the properties that you can find in -the configuration files. - -#### 1. edc.receiver.http.endpoint - -This property is used to define the endpoint where the connector consumer will send the -EndpointDataReference. - -#### 2. edc.dataplane.token.validation.endpoint - -This property is used to define the endpoint exposed by the control plane to validate the token. - -## Run the connectors - -We can start the connectors with the following command: - -```bash -docker compose --profile connectors up -d -``` - -Assuming you didn't change the ports in config files, the consumer will listen on the -ports `29191`, `29192` (management API) and `29292` (IDS API) and the provider will listen on the -ports `12181`, `19182` (management API) and `19282` (IDS API). - -# Run the sample - -Running this sample consists of multiple steps, that are executed one by one and following the same -order. - -> Please in case you have some issues with the jq option, not that it's not mandatory, and you can -> drop it from the command. it's just used to format the output, and the same advice should be -> applied to all calls that use `jq`. - - -### 0. Federated catalog connector - State before datasets are provided by the provider connector - -When the federated catalog connector is started, it will crawl the connectors defined in [nodes-dc.json](federated-catalog/nodes-dc.json). -In our test, this is done for the first time, 5 seconds after startup as defined by "edc.catalog.cache.execution.delay.seconds" in the [config](federated-catalog/catalog-configuration.properties). - -We can request the Federated Catalog with the following request: -```bash -curl 'http://localhost:8181/api/federatedcatalog' \ - -H 'Content-Type: application/json' \ - -d '{"criteria":[]}' \ - -s | jq -``` - -If you do this before the provider connectors have been crawled, then you will get an empty response: -```json -[] -``` - -After the first crawl we get the following response, which contains the connector but no datasets yet: - -```json -[ - { - "@id": "b05dd09e-f1d4-4c6b-9174-3b532480eb7b", - "@type": "dcat:Catalog", - "dcat:dataset": [], - "dcat:service": { - "@id": "c3e3e29b-84c8-4322-af59-7a4c524e190e", - "@type": "dcat:DataService", - "dct:terms": "connector", - "dct:endpointUrl": "http://provider-connector:19194/protocol" - }, - "edc:originator": "http://provider-connector:19194/protocol", - "edc:participantId": "provider", - "@context": { - "dct": "https://purl.org/dc/terms/", - "edc": "https://w3id.org/edc/v0.0.1/ns/", - "dcat": "https://www.w3.org/ns/dcat/", - "odrl": "http://www.w3.org/ns/odrl/2/", - "dspace": "https://w3id.org/dspace/v0.8/" - } - } -] -``` - -### 1. Provider connector - Register data plane instance for provider - -Before a consumer can start talking to a provider, it is necessary to register the data plane -instance of a connector. This is done by sending a POST request to the management API of the -provider connector. The request body should contain the data plane instance of the consumer -connector. - -The registration of the provider data plane instance is done by sending a POST -request to the management API of the connector. - -```bash -curl -H 'Content-Type: application/json' \ - -d '{ - "@context": { - "edc": "https://w3id.org/edc/v0.0.1/ns/" - }, - "@id": "http-pull-provider-dataplane", - "url": "http://provider-connector:19192/control/transfer", - "allowedSourceTypes": [ "HttpData" ], - "allowedDestTypes": [ "HttpProxy", "HttpData" ], - "properties": { - "https://w3id.org/edc/v0.0.1/ns/publicApiUrl": "http://localhost:19291/public/" - } - }' \ - -X POST "http://localhost:19193/management/v2/dataplanes" | -s | jq -``` - -### 2. Consumer connector - Register data plane instance for consumer - -The same thing that is done for the provider must be done for the consumer - -```bash -curl -H 'Content-Type: application/json' \ - -d '{ - "@context": { - "edc": "https://w3id.org/edc/v0.0.1/ns/" - }, - "@id": "http-pull-consumer-dataplane", - "url": "http://consumer-connector:29192/control/transfer", - "allowedSourceTypes": [ "HttpData" ], - "allowedDestTypes": [ "HttpProxy", "HttpData" ], - "properties": { - "https://w3id.org/edc/v0.0.1/ns/publicApiUrl/publicApiUrl": "http://localhost:29291/public/" - } - }' \ - -X POST "http://localhost:29193/management/v2/dataplanes" -``` - -### 3. Provider connector - Create an Asset on the provider side - -The provider connector needs to transfer a file to the location specified by the consumer connector -when the data are requested. In order to offer any data, the provider must maintain an internal list -of resources offered, through a contract offer, the so-called "catalog". - -The following request creates an asset on the provider connector. - -```bash -curl -d '{ - "@context": { - "edc": "https://w3id.org/edc/v0.0.1/ns/" - }, - "asset": { - "@id": "devices", - "properties": { - "name": "device models", - "contenttype": "application/n-quads" - } - }, - "dataAddress": { - "type": "HttpData", - "name": "Test asset", - "baseUrl": "http://ldes-server:8081/devices", - "proxyPath": "true", - "proxyQueryParams": "true", - "contenttype": "application/n-quads", - "header:Accept": "application/n-quads" - } - }' -H 'content-type: application/json' http://localhost:19193/management/v2/assets \ - -s | jq -``` - -> It is important to note that the `baseUrl` property of the `dataAddress` is a fake data used for -> the purpose of this example. It will be the data that the consumer will pull on the sample -> execution. - -Additional properties on `HttpData` can be used to allow consumers to enrich the data request: - -- `proxyPath`: allows specifying additional path segments. -- `proxyQueryParams`: allows specifying query params. -- `proxyBody`: allows attaching a body. -- `proxyMethod`: allows specifying the Http Method (default `GET`) - -### 4. Provider connector - Create a Policy on the provider - -In order to manage the accessibility rules of an asset, it is essential to create a policy. However, -to keep things simple, we will choose a policy that gives direct access to all the assets that are -associated within the contract definitions. -This means that the consumer connector can request any asset from the provider connector. - -```bash -curl -d '{ - "@context": { - "edc": "https://w3id.org/edc/v0.0.1/ns/", - "odrl": "http://www.w3.org/ns/odrl/2/" - }, - "@id": "aPolicy", - "policy": { - "@type": "set", - "odrl:permission": [], - "odrl:prohibition": [], - "odrl:obligation": [] - } - }' -H 'content-type: application/json' http://localhost:19193/management/v2/policydefinitions \ - -s | jq -``` - -### 5. Provider connector - Create a contract definition on Provider - -To ensure an exchange between providers and consumers, the supplier must create a contract offer for -the good, on the basis of which a contract agreement can be negotiated. The contract definition -associates policies to a selection of assets to generate the contract offers that will be put in the -catalog. In this case, the selection is empty, so every asset is attached to these policies - -```bash -curl -d '{ - "@context": { - "edc": "https://w3id.org/edc/v0.0.1/ns/" - }, - "@id": "1", - "accessPolicyId": "aPolicy", - "contractPolicyId": "aPolicy", - "assetsSelector": [] - }' -H 'content-type: application/json' http://localhost:19193/management/v2/contractdefinitions \ - -s | jq -``` - -Sample output: - -```json -{ - ... - "@id": "1", - "edc:createdAt": 1674578184023, - ... -} -``` - -### 6. How to fetch catalog on consumer side - -In order to offer any data, the consumer can fetch the catalog from the provider, that will contain -all the contract offers available for negotiation. In our case, it will contain a single contract -offer, the so-called "catalog". To get the catalog from the consumer side, you can use the following -endpoint: - -```bash -curl -X POST "http://localhost:29193/management/v2/catalog/request" \ - -H 'Content-Type: application/json' \ - -d '{ - "@context": { - "edc": "https://w3id.org/edc/v0.0.1/ns/" - }, - "providerUrl": "http://provider-connector:19194/protocol", - "protocol": "dataspace-protocol-http" - }' -s | jq -``` - -Sample output: - -```json -{ - "@id": "31f6d748-d35b-4dec-9e34-d141fd17b458", - "@type": "dcat:Catalog", - "dcat:dataset": { - "@id": "devices", - "@type": "dcat:Dataset", - "odrl:hasPolicy": { - "@id": "MQ==:ZGV2aWNlcw==:ZDI2Yjc3YWQtMTg1OC00MGI4LWFmMWQtM2U2NTBlZTQwOGFm", - "@type": "odrl:Set", - "odrl:permission": [], - "odrl:prohibition": [], - "odrl:obligation": [], - "odrl:target": "devices" - }, - "dcat:distribution": [ - { - "@type": "dcat:Distribution", - "dct:format": { - "@id": "HttpProxy" - }, - "dcat:accessService": "2a5178c3-c937-4ac2-85be-c46dbc6c5642" - }, - { - "@type": "dcat:Distribution", - "dct:format": { - "@id": "HttpData" - }, - "dcat:accessService": "2a5178c3-c937-4ac2-85be-c46dbc6c5642" - } - ], - "edc:name": "product description", - "edc:id": "devices", - "edc:contenttype": "application/json" - }, - "dcat:service": { - "@id": "2a5178c3-c937-4ac2-85be-c46dbc6c5642", - "@type": "dcat:DataService", - "dct:terms": "connector", - "dct:endpointUrl": "http://provider-connector:19194/protocol" - }, - "edc:participantId": "anonymous", - "@context": { - "dct": "https://purl.org/dc/terms/", - "edc": "https://w3id.org/edc/v0.0.1/ns/", - "dcat": "https://www.w3.org/ns/dcat/", - "odrl": "http://www.w3.org/ns/odrl/2/", - "dspace": "https://w3id.org/dspace/v0.8/" - } -} -``` - -Additionally, the Federated Catalog will now also include this entry. -This may take a couple of seconds as the federated catalog connector only polls the provider every 5 seconds as defined by "edc.catalog.cache.execution.period.seconds" in the [config](federated-catalog/catalog-configuration.properties). - -```bash -curl 'http://localhost:8181/api/federatedcatalog' \ - -H 'Content-Type: application/json' \ - -d '{"criteria":[]}' \ - -s | jq -``` - -should output something like this - -```json -[ - { - "@id": "960d2187-c845-4e1c-9f5e-8beebc83171f", - "@type": "dcat:Catalog", - "dcat:dataset": { - "@id": "devices", - "@type": "dcat:Dataset", - "odrl:hasPolicy": { - "@id": "MQ==:ZGV2aWNlcw==:MWFiNGIwMzYtM2Y1Ni00ZmIwLWJlNzMtYjg5YzM4MTNkMDYz", - "@type": "odrl:Set", - "odrl:permission": [], - "odrl:prohibition": [], - "odrl:obligation": [], - "odrl:target": "devices" - }, - "dcat:distribution": [ - { - "@type": "dcat:Distribution", - "dct:format": { - "@id": "HttpProxy" - }, - "dcat:accessService": "c3e3e29b-84c8-4322-af59-7a4c524e190e" - }, - { - "@type": "dcat:Distribution", - "dct:format": { - "@id": "HttpData" - }, - "dcat:accessService": "c3e3e29b-84c8-4322-af59-7a4c524e190e" - } - ], - "edc:name": "device models", - "edc:id": "devices", - "edc:contenttype": "application/n-quads" - }, - "dcat:service": { - "@id": "c3e3e29b-84c8-4322-af59-7a4c524e190e", - "@type": "dcat:DataService", - "dct:terms": "connector", - "dct:endpointUrl": "http://provider-connector:19194/protocol" - }, - "edc:originator": "http://provider-connector:19194/protocol", - "edc:participantId": "provider", - "@context": { - "dct": "https://purl.org/dc/terms/", - "edc": "https://w3id.org/edc/v0.0.1/ns/", - "dcat": "https://www.w3.org/ns/dcat/", - "odrl": "http://www.w3.org/ns/odrl/2/", - "dspace": "https://w3id.org/dspace/v0.8/" - } - } -] -``` - -### 8. Start the workbench with the LdesClient - -```bash - docker compose up ldio-workbench -d -``` - -Wait for the workbench to start up properly logging "Started Application": -```bash -docker logs --tail 1000 -f $(docker ps -q --filter "name=ldio-workbench$") -``` - -By now you should see a new info log line stating that the pipeline is waiting for a token. -The client will wait for a valid token before it starts consuming the LDES. -To get a token, we need to negotiate a contract and start a transfer. - -### 8. Negotiate a contract - -In order to request any data, a contract gets negotiated, and an agreement is resulting has to be -negotiated between providers and consumers. - -The consumer now needs to initiate a contract negotiation sequence with the provider. That sequence -looks as follows: - -1. Consumer sends a contract offer to the provider (__currently, this has to be equal to the - provider's offer!__) -2. Provider validates the received offer against its own offer -3. Provider either sends an agreement or a rejection, depending on the validation result -4. In case of successful validation, provider and consumer store the received agreement for later - 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. - -```bash -curl -d '{ - "@context": { - "edc": "https://w3id.org/edc/v0.0.1/ns/", - "odrl": "http://www.w3.org/ns/odrl/2/" - }, - "@type": "NegotiationInitiateRequestDto", - "connectorId": "provider", - "connectorAddress": "http://provider-connector:19194/protocol", - "consumerId": "consumer", - "providerId": "provider", - "protocol": "dataspace-protocol-http", - "offer": { - "offerId": "MQ==:ZGV2aWNlcw==:ZDI2Yjc3YWQtMTg1OC00MGI4LWFmMWQtM2U2NTBlZTQwOGFm", - "assetId": "devices", - "policy": { - "@id": "MQ==:ZGV2aWNlcw==:ZDI2Yjc3YWQtMTg1OC00MGI4LWFmMWQtM2U2NTBlZTQwOGFm", - "@type": "Set", - "odrl:permission": [], - "odrl:prohibition": [], - "odrl:obligation": [], - "odrl:target": "devices" - } - } -}' -X POST -H 'content-type: application/json' http://localhost:29193/management/v2/contractnegotiations \ --s | jq -``` - -Sample output: - -```json -{ - ... - "@id": "254015f3-5f1e-4a59-9ad9-bf0e42d4819e", - "edc:createdAt": 1685525281848, - ... -} -``` - -### 9. Getting the contract agreement id - -After calling the endpoint for initiating a contract negotiation, we get a UUID as the response. -This UUID is the ID of the ongoing contract negotiation between consumer and provider. The -negotiation sequence between provider and consumer is executed asynchronously in the background by a -state machine. Once both provider and consumer either reach the `confirmed` or the `declined` -state, the negotiation is finished. We can now use the UUID to check the current status of the -negotiation using an endpoint on the consumer side. - -```bash -curl -X GET "http://localhost:29193/management/v2/contractnegotiations/" \ - --header 'Content-Type: application/json' \ - -s | jq -``` - -Sample output: - -```json -{ - "@type": "edc:ContractNegotiationDto", - "@id": "5ca21b82-075b-4682-add8-c26c9a2ced67", - "edc:type": "CONSUMER", - "edc:protocol": "dataspace-protocol-http", - "edc:state": "FINALIZED", - "edc:counterPartyAddress": "http://provider-connector:19194/protocol", - "edc:callbackAddresses": [], - "edc:contractAgreementId": "MQ==:ZGV2aWNlcw==:ZDI2Yjc3YWQtMTg1OC00MGI4LWFmMWQtM2U2NTBlZTQwOGFm", - "@context": { - "dct": "https://purl.org/dc/terms/", - "edc": "https://w3id.org/edc/v0.0.1/ns/", - "dcat": "https://www.w3.org/ns/dcat/", - "odrl": "http://www.w3.org/ns/odrl/2/", - "dspace": "https://w3id.org/dspace/v0.8/" - } -} -``` - -### 10. Start the transfer - -Now that we have a contract agreement and our client is running, -we can finally start consuming the LDES. In the request body, we need -to specify which asset we want transferred, the ID of the contract agreement, the address of the -provider connector and where we want the file transferred. You will find the request body below. -Before executing the request, insert the contract agreement ID from the previous step. Then run : - -> the "HttpProxy" method is used for the consumer pull method, and it means that it will be up to -> the consumer to request the data to the provider and that the request will be a proxy for the -> datasource - -```bash -curl -X POST "http://localhost:8082/client-pipeline/transfer" \ - -H "Content-Type: application/json" \ - -d '{ - "@context": { - "@vocab": "https://w3id.org/edc/v0.0.1/ns/" - }, - "@type": "TransferRequest", - "connectorId": "provider", - "connectorAddress": "http://provider-connector:19194/protocol", - "contractId": "MQ==:ZGV2aWNlcw==:Nzk4N2UwODgtNDY5Ni00ZTllLTkxNWItMTRlY2NkYzFlYzk5", - "assetId": "devices", - "protocol": "dataspace-protocol-http", - "dataDestination": { - "@type": "DataAddress", - "type": "HttpProxy" - }, - "privateProperties": { - "receiverHttpEndpoint" : "http://ldio-workbench:8082/client-pipeline/token" - } - }' \ - -s | jq -``` - -Then, we will get a UUID in the response. This time, this is the ID of the `TransferProcess` ( -process id) created on the consumer -side, because like the contract negotiation, the data transfer is handled in a state machine and -performed asynchronously. - -Sample output: - -```json -{ - ... - "@id": "591bb609-1edb-4a6b-babe-50f1eca3e1e9", - "edc:createdAt": 1674078357807, - ... -} -``` - -### 11. Check the transfer status - -Due to the nature of the transfer, it will be very fast and most likely already done by the time you -read the UUID. - -```bash -curl http://localhost:29193/management/v2/transferprocesses/ -``` - - -You should see the Transfer Process in `COMPLETED` state: -```json -{ - ... - "@id": "0f648d82-23b4-464d-8f7b-c89860efe7c9", - "edc:state": "COMPLETED", - ... -} - -``` - -### 12. View results in the workbench logs - -```bash -docker logs --tail 1000 -f $(docker ps -q --filter "name=ldio-workbench$") -``` - -# Test Teardown -To stop all systems use: -```bash -docker compose --profile connectors down -docker compose --profile delay-started down -docker compose down -``` \ No newline at end of file diff --git a/e2e-test/certs/cert.pem b/e2e-test/certs/cert.pem deleted file mode 100644 index c7dc26f..0000000 --- a/e2e-test/certs/cert.pem +++ /dev/null @@ -1,21 +0,0 @@ ------BEGIN CERTIFICATE----- -MIIDazCCAlOgAwIBAgIUZ3/sZXYzW4PjmOXKrZn6WBmUJ+4wDQYJKoZIhvcNAQEL -BQAwRTELMAkGA1UEBhMCQVUxEzARBgNVBAgMClNvbWUtU3RhdGUxITAfBgNVBAoM -GEludGVybmV0IFdpZGdpdHMgUHR5IEx0ZDAeFw0yMjAyMjMxNTA2MDNaFw0zMjAy -MjExNTA2MDNaMEUxCzAJBgNVBAYTAkFVMRMwEQYDVQQIDApTb21lLVN0YXRlMSEw -HwYDVQQKDBhJbnRlcm5ldCBXaWRnaXRzIFB0eSBMdGQwggEiMA0GCSqGSIb3DQEB -AQUAA4IBDwAwggEKAoIBAQDBl6XaJnXTL+6DWip3aBhU+MzmY4d1V9hbTm1tiZ3g -E0VbUrvGO3LoYaxpPv6zFmsg3uJv6JxVAde7EddidN0ITHB9cQNdAfdUJ5njmsGS -PbdQuOQTHw0aG7/QvTI/nsvfEE6e0lbV/0e7DHacZT/+OztBH1RwkG2ymM94Hf8H -I6x7q6yfRTAZOqeOMrPCYTcluAgE9NskoPvjX5qASakBtXISKIsOU84N0/2HDN3W -EGMXvoHUQu6vrij6BwiwxKaw1AKwWENKoga775bPXN3M+JTSaIKE7dZbKzvx0Zi0 -h5X+bxc3BJi3Z/CsUBCzE+Y0SFetOiYmyl/2YmnneYoVAgMBAAGjUzBRMB0GA1Ud -DgQWBBTvK1wVERwjni4B2vdH7KtEJeVWFzAfBgNVHSMEGDAWgBTvK1wVERwjni4B -2vdH7KtEJeVWFzAPBgNVHRMBAf8EBTADAQH/MA0GCSqGSIb3DQEBCwUAA4IBAQBn -QHiPA7OBYukHd9gS7c0HXE+fsWcS3GZeLqcHfQQnV3pte1vTmu9//IVW71wNCJ1/ -rySRyODPQoPehxEcyHwupNZSzXK//nPlTdSgjMfFxscvt1YndyQLQYCfyOJMixAe -Aqrb14GTFHUUrdor0PyElhkULjkOXUrSIsdBrfWrwLTkelE8NK3tb5ZG8KPzD9Jy -+NwEPPr9d+iHkUkM7EFWw/cl56wka9ryBb97RI7DqbO6/j6OXHMk4GByxKv7DSIR -IvF9/Dw20qytajtaHV0pluFcOBuFc0NfiDvCaQlbTsfjzbc6UmZWbOi9YOJl3VQ/ -g3h+15GuzbsSzOCOEYOT ------END CERTIFICATE----- diff --git a/e2e-test/certs/cert.pfx b/e2e-test/certs/cert.pfx deleted file mode 100644 index 7ac9c73e0eb6b5c2fa625d818e42d55bdafc8a2b..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 2477 zcmY+^c{J3G8V7K*W@N}R7=$7FHnNl@TSGL2Fj;DNOC*GhE&IP}zqvy)xzv zQL;p;A(BR~v1ZAx(5-Xsz3;t$Jm)#*`#tCR@A+T>L=6}O!2$?>I6^7OB54~5Is~Es z2zMxexcDn}!U9m>;!u#NoRD=ju#8QFzm^2$y49g1TMv z=T@sTo@Iuph_A%yU=lxc7M{sJMHUT>F|}KXUgo$hFFS>A2!j7*6*i&bNm83Pw2;<1 zlD}V5KUbh&o|jOxsP+BiwXBG4&`tucGj8`-Hm@xYJ}`H^&q$4GmUu<1YCBvj`C$0i zkFsaL3jy!*E?2AUSW6Pe-Zjg?APSh+Uhq-Q)U@7jmt#8E>T$EH6!|pKz~;1w=$~nhB-?cONKvYWB(}r)QbC0-GdWIqew0w+G5Wq#m^rPtZ{$ z&t3^ej`3$~G<<2pp49+5+q{j;Rh)KZXRnVO3qF5>eHL=xcsdXrkEpgxwm0V8`ssk6Z8vc4Et<{a&YT958$yF6j}K( z4hN^-U5JL_{5>%{Y?3HMe0}$$xMM|0Q~;4aZqhSedSM+=_Eg(Xx&_xr&h4{kQ6=Zy zW@OQ7;(7v+Fweo zb}gS9>{w6uxhvyvlziQ9z-3d+n125oDs)1&%G zEwA3(y*}qIWtKDR8WA@gI9QkkDNyw1yM+2Q51Ffz7>M>4w=m^={|4pZ%S)yOfKw=S zz69`I8q8wN^N`NiDcpnDll_@y_Lt-uFCKP{LaIrnK#~AY;j~X%jH{UC%6?YFF(6`J zeO0vTRy6aht=iu+Gn1WZZ9${yya0`i>EAky_j=kWwxgJ@qBH-e;dkS@+_oyS3!Aiw z;flVSZ2Gwg5uLIPua4c7LXmk++;IQ)ShM>oI!v-Ny??463&2eN=kX~3>^KyFsr`zT zevKUb@P8QK0)c;dvHXjWh5yq5@>_>7Tkb5#{9e;<9iRa8RoC_4ISv`^=M(qQdQ#2V zIza+e3IWHj4>i1V?+l92n8{c(>>O7{qXrb~$} z8V6i+B42m1p07qSh%@E`sm?9n2@PvNYy1jX*e|%F=6kUedQy;Iln(yLlX1`aN#?b- zZwXNhKWgoMN~ESsM{=(WNU3B-P_1gdul?TFtyYb>%F_uP1wj4yp>Z!i6*k*Ul%Gz)g&^5L%mg;3Yei{>pW3}~9}Fie!CscOnc zJgrKau67c@sA=-R{3>m^F}gVEM{D)BD;Rfv&5G3Fy=WURVqP6QJxj82TTmc;y4Q1- zx|64G<-u>)G8wNcEv5P}fF>N`2APM^GsZsD9(GGFY8a1t-ibjD#{`UD_>(v-XlYzo zA;v?EMrJqVD#h=r6cyea-Ed8TH>Zq;HKlDnF#HM0hMbMSu#w}iv=RZVfG{~?FaJbD zMa^hLzlX||5&8d(&Eyl0P5RU*~LQSx?Wln6}c1 zjE%SIZYd-En@6!L4H>W9OOz7Uh%swV~-_xx9L37=5~uCx-Us8{Wfv z!)kuI6u*;E^(MO0p!ubmp{22ExfFD%2=4oC9Gi#0bMN>{7MOeNuCxxli^wSO z#`0sH5ncdKZJqBDq$!_D$m6M1M9n|sZbu%mtl$5t$fH@XWMBH^*&PYhQKlKIzN#AS zP+p19Vo>>tV1Zg+=2Mjn;E1Epntc)Ceohe56KASXPy5a+R<=Vut-5#zROAXC2-6Qq!-V_HxY5dt)>gm+(P2v_EXSK~h`}Bm!(8j7N zDp}fG?p^A7UZ|tg4P;$YSJ-!8MYi_%t?<-l^SUW^yH23Ug-IiYTF2H#qp7+WS4$R* zaAti?s5msEyR0#3X@J~V5>*x`)cC0CVNqh9tGDxxLcyCjv}KFV2j%^Du{Tt5oE7^+ z;-xx^OdO|Xz6kXWC+|Nr=h33y@q4B#HOS`(w#wQyP1IL;yd7dDd?TSkv`?1vgrI`tLtzxEjlPjW_Z(lo%ao_L5vmNUfyH1EaF{X=1S|^U nfC>)L0b!m6KEg{. -@prefix xsd: . - - a tree:Node ; - tree:viewDescription [ a tree:ViewDescription ; - tree:fragmentationStrategy () ; - tree:pageSize "100"^^ ; -] . diff --git a/e2e-test/config/devices.ttl b/e2e-test/config/devices.ttl deleted file mode 100644 index e0d9932..0000000 --- a/e2e-test/config/devices.ttl +++ /dev/null @@ -1,10 +0,0 @@ -@prefix ldes: . -@prefix tree: . -@prefix dcterms: . -@prefix prov: . -@prefix sh: . - - a ldes:EventStream ; - tree:shape [ a sh:NodeShape ; sh:targetClass ] ; - ldes:timestampPath prov:generatedAtTime ; - ldes:versionOfPath dcterms:isVersionOf . diff --git a/e2e-test/config/ldes-server.config.yml b/e2e-test/config/ldes-server.config.yml deleted file mode 100644 index 2bee348..0000000 --- a/e2e-test/config/ldes-server.config.yml +++ /dev/null @@ -1,19 +0,0 @@ -mongock: - migration-scan-package: VSDS -springdoc: - swagger-ui: - path: /v1/swagger -management: - tracing: - enabled: false -ldes-server: - host-name: http://localhost:8081 -spring: - data: - mongodb: - database: iow - host: ldes-mongodb - port: 27017 - -server: - port: 8081 diff --git a/e2e-test/config/seed.sh b/e2e-test/config/seed.sh deleted file mode 100755 index 384aba1..0000000 --- a/e2e-test/config/seed.sh +++ /dev/null @@ -1,14 +0,0 @@ -#!/bin/bash -export SCRIPT_PATH=$(dirname -- "$( readlink -f -- "${BASH_SOURCE:-$0}"; )") - -curl --fail -X POST 'http://localhost:8081/admin/api/v1/eventstreams' -H 'Content-Type: text/turtle' -d "@$SCRIPT_PATH/devices.ttl" -code=$? -if [ $code != 0 ] - then exit $code -fi - -curl --fail -X POST 'http://localhost:8081/admin/api/v1/eventstreams/devices/views' -H 'Content-Type: text/turtle' -d "@$SCRIPT_PATH/devices.paged.ttl" -code=$? -if [ $code != 0 ] - then exit $code -fi diff --git a/e2e-test/data/device.template.json b/e2e-test/data/device.template.json deleted file mode 100644 index c825d1a..0000000 --- a/e2e-test/data/device.template.json +++ /dev/null @@ -1,109 +0,0 @@ -{ - "@context": [ - "https://json-ld.org/test-suite/context.jsonld", - "https://uri.etsi.org/ngsi-ld/v1/ngsi-ld-core-context.jsonld" - ], - "id": "urn:ngsi-v2:cot-imec-be:Device:imec-iow-UR5gEycRuaafxnhvjd9jnU:{{index}}", - "type": "Device", - "adminState": { - "type": "Property", - "value": "down" - }, - "alternativeIds": { - "type": "Property", - "value": [ - "simcard.206012902136977", - "octa_dec.2336861766884020237" - ] - }, - "batteryLevel": { - "type": "Property", - "value": 0.32, - "rawValue": { - "type": "Property", - "value": "3192" - }, - "rawValueUnitCode": { - "type": "Property", - "value": "2Z" - } - }, - "calibrationParameters": { - "type": "Property", - "value": { - "battery": { - "gain": 600, - "offset": 3000 - } - } - }, - "copyObservationAttributes": { - "type": "Property", - "value": [ - "batteryLevel" - ] - }, - "dateLastValueReported": { - "type": "Property", - "value": { - "@type": "DateTime", - "@value": "{{timestamp}}" - } - }, - "extraMeasurementAttributes": { - "type": "Property", - "value": { - "location": true, - "locationName": true, - "samplingPoint": true - } - }, - "healthState": { - "type": "Property", - "value": "up" - }, - "location": { - "type": "GeoProperty", - "value": { - "type": "Point", - "coordinates": [ - 5.4563, - 51.41363 - ] - }, - "name": { - "type": "Property", - "value": "loc-00056-19" - } - }, - "locationName": { - "type": "Property", - "value": "loc-00056-19" - }, - "maxTimeBetweenObservations": { - "type": "Property", - "value": 60 - }, - "name": { - "type": "Property", - "value": "box-00145-49" - }, - "owner": { - "type": "Property", - "value": [ - "imec" - ] - }, - "refDeviceModel": { - "type": "Relationship", - "object": "urn:ngsi-v2:cot-imec-be:devicemodel:imec-iow-box-v0003" - }, - "samplingPoint": { - "type": "Property", - "value": "spt-00000-87" - }, - "source": { - "type": "Property", - "value": "cot.iow.observed" - } -} \ No newline at end of file diff --git a/e2e-test/docker-compose.yml b/e2e-test/docker-compose.yml deleted file mode 100644 index 4c4f2d9..0000000 --- a/e2e-test/docker-compose.yml +++ /dev/null @@ -1,157 +0,0 @@ -version: '3.3' -services: - - provider-connector: - container_name: connector_provider-connector - image: vsds-dataspace-connector:local - build: - context: .. - dockerfile: http-pull-connector/Dockerfile - environment: - - EDC_KEYSTORE=certs/cert.pfx - - EDC_KEYSTORE_PASSWORD=123456 - - EDC_VAULT=http-pull-provider/provider-vault.properties - - EDC_FS_CONFIG=http-pull-provider/provider-configuration.properties - ports: - - 19191:19191 - - 19193:19193 - - 19194:19194 - - 19291:19291 - - 19192:19192 - volumes: - - ./certs/cert.pfx:/app/certs/cert.pfx - - ./http-pull-provider/provider-configuration.properties:/app/http-pull-provider/provider-configuration.properties - - ./http-pull-provider/provider-vault.properties:/app/http-pull-provider/provider-vault.properties - networks: - - ldes - profiles: - - connectors - - consumer-connector: - container_name: connector_consumer-connector - image: vsds-dataspace-connector:local - build: - context: .. - dockerfile: http-pull-connector/Dockerfile - environment: - - EDC_KEYSTORE=certs/cert.pfx - - EDC_KEYSTORE_PASSWORD=123456 - - EDC_VAULT=http-pull-consumer/consumer-vault.properties - - EDC_FS_CONFIG=http-pull-consumer/consumer-configuration.properties - ports: - - 29191:29191 - - 29193:29193 - - 29194:29194 - - 29291:29291 - - 29192:29192 - volumes: - - ./certs/cert.pfx:/app/certs/cert.pfx - - ./http-pull-consumer/consumer-configuration.properties:/app/http-pull-consumer/consumer-configuration.properties - - ./http-pull-consumer/consumer-vault.properties:/app/http-pull-consumer/consumer-vault.properties - networks: - - ldes - profiles: - - connectors - - federated-catalog-connector: - container_name: federated-catalog-connector - image: vsds-federated-catalog-connector:local - build: - context: .. - dockerfile: federated-catalog-connector/Dockerfile - environment: - - EDC_FS_CONFIG=config/catalog-configuration.properties - - FCC_DIRECTORY_FILE=config/nodes-dc.json - depends_on: [ provider-connector ] - volumes: - - ./federated-catalog/catalog-configuration.properties:/app/config/catalog-configuration.properties - - ./federated-catalog/nodes-dc.json:/app/config/nodes-dc.json - ports: - - "8181:8181" - networks: - - ldes - profiles: - - connectors - - test-message-generator: - container_name: connector_test-message-generator - image: ghcr.io/informatievlaanderen/test-message-generator:latest - environment: - - TARGETURL=http://ldio-server-seeder:8080/seed-server - - SILENT=false - - CRON=* * * * * * - - TEMPLATEFILE=/tmp/data/device.template.json - - MIMETYPE=application/ld+json - volumes: - - ./data/device.template.json:/tmp/data/device.template.json:ro - networks: - - ldes - profiles: - - delay-started - - ldio-server-seeder: - image: ghcr.io/informatievlaanderen/ldi-orchestrator:latest - container_name: connector_ldio-server-seeder - volumes: - - ./ldio-server-seeder.yml:/ldio/config/application.yml:ro - networks: - - ldes - depends_on: - - ldes-server - - ldes-server: - container_name: connector_ldes-server - image: ghcr.io/informatievlaanderen/ldes-server:latest - environment: - - SIS_DATA=/tmp - volumes: - - ./config/ldes-server.config.yml:/application.yml:ro - - ./data/epsg:/tmp/Databases:rw - ports: - - 8081:8081 # needed for admin API - networks: - - ldes - depends_on: - - ldes-mongodb - - ldes-mongodb: - container_name: connector_ldes-mongodb - image: mongo:latest - ports: - - 27017:27017 - networks: - - ldes - - nifi-workbench: - image: ghcr.io/informatievlaanderen/ldi-workbench-nifi:latest - container_name: connector_nifi-workbench - environment: - - NIFI_WEB_HTTP_PORT=8000 - volumes: - - ../../data/scripts/nifi-env.sh:/opt/nifi/nifi-current/bin/nifi-env.sh:ro - ports: - - 8000:8000 - - 8082:8080 - networks: - - ldes - profiles: - - delay-started - - ldio-workbench: - image: ldes/ldi-orchestrator:1.10.0-SNAPSHOT - container_name: connector_ldio-workbench - environment: - - SPRING_CONFIG_NAME=application - - SPRING_CONFIG_LOCATION=/config/ - volumes: - - ./ldio-config.yml:/config/application.yml:ro - ports: - - 8082:8082 - networks: - - ldes - profiles: - - delay-started - -networks: - ldes: - name: ldes_connector_network \ No newline at end of file diff --git a/e2e-test/federated-catalog/catalog-configuration.properties b/e2e-test/federated-catalog/catalog-configuration.properties deleted file mode 100644 index 8117c0b..0000000 --- a/e2e-test/federated-catalog/catalog-configuration.properties +++ /dev/null @@ -1,6 +0,0 @@ -edc.catalog.cache.execution.delay.seconds=5 -edc.catalog.cache.execution.period.seconds=5 -edc.catalog.cache.partition.num.crawlers=1 -edc.ids.id=urn:connector:fcc -edc.web.rest.cors.enabled=true -edc.web.rest.cors.headers="origin,content-type,accept,authorization,x-api-key" \ No newline at end of file diff --git a/e2e-test/federated-catalog/nodes-dc.json b/e2e-test/federated-catalog/nodes-dc.json deleted file mode 100644 index c05fec3..0000000 --- a/e2e-test/federated-catalog/nodes-dc.json +++ /dev/null @@ -1,9 +0,0 @@ -[ - { - "name": "provider-connector", - "url": "http://provider-connector:19194/protocol", - "supportedProtocols": [ - "dataspace-protocol-http" - ] - } -] diff --git a/e2e-test/http-pull-consumer/consumer-configuration.properties b/e2e-test/http-pull-consumer/consumer-configuration.properties deleted file mode 100644 index 07a3ebf..0000000 --- a/e2e-test/http-pull-consumer/consumer-configuration.properties +++ /dev/null @@ -1,18 +0,0 @@ -edc.participant.id=consumer -edc.ids.id=urn:connector:consumer -edc.dsp.callback.address=http://consumer-connector:29194/protocol -web.http.port=29191 -web.http.path=/api -web.http.management.port=29193 -web.http.management.path=/management -web.http.protocol.port=29194 -web.http.protocol.path=/protocol -edc.public.key.alias=public-key -edc.transfer.dataplane.token.signer.privatekey.alias=1 -edc.transfer.proxy.token.signer.privatekey.alias=1 -edc.transfer.proxy.token.verifier.publickey.alias=public-key -web.http.public.port=29291 -web.http.public.path=/public -web.http.control.port=29192 -web.http.control.path=/control -edc.dataplane.token.validation.endpoint=http://consumer-connector:29192/control/token diff --git a/e2e-test/http-pull-consumer/consumer-vault.properties b/e2e-test/http-pull-consumer/consumer-vault.properties deleted file mode 100644 index 6ebdebd..0000000 --- a/e2e-test/http-pull-consumer/consumer-vault.properties +++ /dev/null @@ -1 +0,0 @@ -public-key=-----BEGIN CERTIFICATE-----\r\nMIIDazCCAlOgAwIBAgIUZ3/sZXYzW4PjmOXKrZn6WBmUJ+4wDQYJKoZIhvcNAQEL\r\nBQAwRTELMAkGA1UEBhMCQVUxEzARBgNVBAgMClNvbWUtU3RhdGUxITAfBgNVBAoM\r\nGEludGVybmV0IFdpZGdpdHMgUHR5IEx0ZDAeFw0yMjAyMjMxNTA2MDNaFw0zMjAy\r\nMjExNTA2MDNaMEUxCzAJBgNVBAYTAkFVMRMwEQYDVQQIDApTb21lLVN0YXRlMSEw\r\nHwYDVQQKDBhJbnRlcm5ldCBXaWRnaXRzIFB0eSBMdGQwggEiMA0GCSqGSIb3DQEB\r\nAQUAA4IBDwAwggEKAoIBAQDBl6XaJnXTL+6DWip3aBhU+MzmY4d1V9hbTm1tiZ3g\r\nE0VbUrvGO3LoYaxpPv6zFmsg3uJv6JxVAde7EddidN0ITHB9cQNdAfdUJ5njmsGS\r\nPbdQuOQTHw0aG7/QvTI/nsvfEE6e0lbV/0e7DHacZT/+OztBH1RwkG2ymM94Hf8H\r\nI6x7q6yfRTAZOqeOMrPCYTcluAgE9NskoPvjX5qASakBtXISKIsOU84N0/2HDN3W\r\nEGMXvoHUQu6vrij6BwiwxKaw1AKwWENKoga775bPXN3M+JTSaIKE7dZbKzvx0Zi0\r\nh5X+bxc3BJi3Z/CsUBCzE+Y0SFetOiYmyl/2YmnneYoVAgMBAAGjUzBRMB0GA1Ud\r\nDgQWBBTvK1wVERwjni4B2vdH7KtEJeVWFzAfBgNVHSMEGDAWgBTvK1wVERwjni4B\r\n2vdH7KtEJeVWFzAPBgNVHRMBAf8EBTADAQH/MA0GCSqGSIb3DQEBCwUAA4IBAQBn\r\nQHiPA7OBYukHd9gS7c0HXE+fsWcS3GZeLqcHfQQnV3pte1vTmu9//IVW71wNCJ1/\r\nrySRyODPQoPehxEcyHwupNZSzXK//nPlTdSgjMfFxscvt1YndyQLQYCfyOJMixAe\r\nAqrb14GTFHUUrdor0PyElhkULjkOXUrSIsdBrfWrwLTkelE8NK3tb5ZG8KPzD9Jy\r\n+NwEPPr9d+iHkUkM7EFWw/cl56wka9ryBb97RI7DqbO6/j6OXHMk4GByxKv7DSIR\r\nIvF9/Dw20qytajtaHV0pluFcOBuFc0NfiDvCaQlbTsfjzbc6UmZWbOi9YOJl3VQ/\r\ng3h+15GuzbsSzOCOEYOT\r\n-----END CERTIFICATE----- diff --git a/e2e-test/http-pull-provider/provider-configuration.properties b/e2e-test/http-pull-provider/provider-configuration.properties deleted file mode 100644 index 3f9b8d7..0000000 --- a/e2e-test/http-pull-provider/provider-configuration.properties +++ /dev/null @@ -1,18 +0,0 @@ -edc.participant.id=provider -edc.ids.id=urn:connector:provider -edc.dsp.callback.address=http://provider-connector:19194/protocol -web.http.port=19191 -web.http.path=/api -web.http.management.port=19193 -web.http.management.path=/management -web.http.protocol.port=19194 -web.http.protocol.path=/protocol -edc.public.key.alias=public-key -edc.transfer.dataplane.token.signer.privatekey.alias=1 -edc.transfer.proxy.token.signer.privatekey.alias=1 -edc.transfer.proxy.token.verifier.publickey.alias=public-key -web.http.public.port=19291 -web.http.public.path=/public -web.http.control.port=19192 -web.http.control.path=/control -edc.dataplane.token.validation.endpoint=http://provider-connector:19192/control/token diff --git a/e2e-test/http-pull-provider/provider-vault.properties b/e2e-test/http-pull-provider/provider-vault.properties deleted file mode 100644 index 6ebdebd..0000000 --- a/e2e-test/http-pull-provider/provider-vault.properties +++ /dev/null @@ -1 +0,0 @@ -public-key=-----BEGIN CERTIFICATE-----\r\nMIIDazCCAlOgAwIBAgIUZ3/sZXYzW4PjmOXKrZn6WBmUJ+4wDQYJKoZIhvcNAQEL\r\nBQAwRTELMAkGA1UEBhMCQVUxEzARBgNVBAgMClNvbWUtU3RhdGUxITAfBgNVBAoM\r\nGEludGVybmV0IFdpZGdpdHMgUHR5IEx0ZDAeFw0yMjAyMjMxNTA2MDNaFw0zMjAy\r\nMjExNTA2MDNaMEUxCzAJBgNVBAYTAkFVMRMwEQYDVQQIDApTb21lLVN0YXRlMSEw\r\nHwYDVQQKDBhJbnRlcm5ldCBXaWRnaXRzIFB0eSBMdGQwggEiMA0GCSqGSIb3DQEB\r\nAQUAA4IBDwAwggEKAoIBAQDBl6XaJnXTL+6DWip3aBhU+MzmY4d1V9hbTm1tiZ3g\r\nE0VbUrvGO3LoYaxpPv6zFmsg3uJv6JxVAde7EddidN0ITHB9cQNdAfdUJ5njmsGS\r\nPbdQuOQTHw0aG7/QvTI/nsvfEE6e0lbV/0e7DHacZT/+OztBH1RwkG2ymM94Hf8H\r\nI6x7q6yfRTAZOqeOMrPCYTcluAgE9NskoPvjX5qASakBtXISKIsOU84N0/2HDN3W\r\nEGMXvoHUQu6vrij6BwiwxKaw1AKwWENKoga775bPXN3M+JTSaIKE7dZbKzvx0Zi0\r\nh5X+bxc3BJi3Z/CsUBCzE+Y0SFetOiYmyl/2YmnneYoVAgMBAAGjUzBRMB0GA1Ud\r\nDgQWBBTvK1wVERwjni4B2vdH7KtEJeVWFzAfBgNVHSMEGDAWgBTvK1wVERwjni4B\r\n2vdH7KtEJeVWFzAPBgNVHRMBAf8EBTADAQH/MA0GCSqGSIb3DQEBCwUAA4IBAQBn\r\nQHiPA7OBYukHd9gS7c0HXE+fsWcS3GZeLqcHfQQnV3pte1vTmu9//IVW71wNCJ1/\r\nrySRyODPQoPehxEcyHwupNZSzXK//nPlTdSgjMfFxscvt1YndyQLQYCfyOJMixAe\r\nAqrb14GTFHUUrdor0PyElhkULjkOXUrSIsdBrfWrwLTkelE8NK3tb5ZG8KPzD9Jy\r\n+NwEPPr9d+iHkUkM7EFWw/cl56wka9ryBb97RI7DqbO6/j6OXHMk4GByxKv7DSIR\r\nIvF9/Dw20qytajtaHV0pluFcOBuFc0NfiDvCaQlbTsfjzbc6UmZWbOi9YOJl3VQ/\r\ng3h+15GuzbsSzOCOEYOT\r\n-----END CERTIFICATE----- diff --git a/e2e-test/ldio-config.yml b/e2e-test/ldio-config.yml deleted file mode 100644 index 4f95049..0000000 --- a/e2e-test/ldio-config.yml +++ /dev/null @@ -1,19 +0,0 @@ -server: - port: 8082 -orchestrator: - pipelines: - - name: client-pipeline - description: "Simple LdioLdesClientConnector in, console out pipeline." - input: - name: be.vlaanderen.informatievlaanderen.ldes.ldio.LdioLdesClientConnector - config: - url: http://consumer-connector:29291/public - connector-transfer-url: http://consumer-connector:29193/management/v2/transferprocesses - proxy-url-to-replace: http://localhost:8081/devices - proxy-url-replacement: http://consumer-connector:29291/public - source-format: application/n-quads - outputs: - - name: be.vlaanderen.informatievlaanderen.ldes.ldio.LdioConsoleOut - config: - rdf-writer: - content-type: text/turtle \ No newline at end of file diff --git a/e2e-test/ldio-server-seeder.yml b/e2e-test/ldio-server-seeder.yml deleted file mode 100644 index 93ffd0e..0000000 --- a/e2e-test/ldio-server-seeder.yml +++ /dev/null @@ -1,23 +0,0 @@ -server: - port: 8080 -orchestrator: - pipelines: - - name: seed-server - description: "Simple http in, version creation, http out pipeline allowing to pause output." - input: - name: be.vlaanderen.informatievlaanderen.ldes.ldio.LdioHttpIn - adapter: - name: be.vlaanderen.informatievlaanderen.ldes.ldi.RdfAdapter - transformers: - - name: be.vlaanderen.informatievlaanderen.ldes.ldi.VersionObjectCreator - config: - member-type: https://uri.etsi.org/ngsi-ld/default-context/Device - delimiter: "/" - date-observed-property: "" - generatedAt-property: http://www.w3.org/ns/prov#generatedAtTime - versionOf-property: http://purl.org/dc/terms/isVersionOf - outputs: - - name: be.vlaanderen.informatievlaanderen.ldes.ldio.LdioHttpOut - config: - content-type: application/n-quads - endpoint: http://ldes-server:8081/devices \ No newline at end of file