Refactoring notification flow EDC provider

mkanal commented 6 months ago

A clear and concise description of what the desired story will look like. --> As team I want to create the catalog offer in the EDC provider instance so that** to confirm with the C-X network architecture

Hints / Details

Currently the edc consumer is used for persisting catalog offer for notifications. This should be done within the edc provider.

Acceptance Criteria

[x] Edc Provider is used for contract creation
[x] Edc Consumer does not hold the catalogoffer for notifications
[x] Setup for Dev, Test, E2E-A, E2E-B, INT-A, INT-B
[x] Wiremock is reset to only use edc provider

Out of Scope

...

mkanal commented 6 months ago

@ds-mwesener Please add the following to the story

Link

blocks https://github.com/eclipse-tractusx/traceability-foss/issues/511

ds-mwesener commented 6 months ago

Hi @ds-crehm, feature has been installed on e2e environments. Please test.

Steps to validate:

1) Using insomnia collection EDC.getCatalog with the consumers Expected behaviour: No catalog offers there 2) Using insomnia collection EDC.getCatalog with the providers Expected behaviour: Catalog Offers for Notifications exist

ds-crehm commented 6 months ago

Test successful. No catalog offers for consumers: grafik Existing catalog offers for providers: grafik Tested on DEV, TEST, E2E-A, E2E-B.

eclipse-tractusx / traceability-foss