Standalone Catalog Runtime

zeier commented 2 years ago

Upstream https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/issues/995

Description

One of the deployments to be supported for the MVD is to have the Federated Catalog Service to be run as a dedicated service (see agera-edc/MinimumViableDataspace#2). The EDC currently only supports catalogs which are embedded in the connector runtime.

To cover the deployment of a standalone catalog runtime for the MVD, a corresponding launcher is required including integration with the connector runtime.

Acceptance Criteria

[ ] ADR on the design
[ ] The Federated Catalog Service can be hosted as a dedicated process (single instance)
[ ] Integration with the connector runtime
[ ] Integration tests with the connector and catalog running as dedicated processes
[ ] Upstream issue https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/issues/995 is covered

Tasks

[ ] ADR
[ ] Implement RemoteCacheQueryAdapter (API client SDK)
[ ] implement a catalog API
[ ] Unit tests
[ ] Integration tests
[ ] Add launcher with Dockerfile

algattik commented 2 years ago

A big question would be how do we do ACLs with a centralised catalog? Perhaps it's better not to do this, so that each participant can decide which asset they want their peers to see?

github-actions[bot] commented 2 years ago

This issue is stale because it has been open for 14 days with no activity.

zeier commented 2 years ago

Closing, as it is not planned to cover this item by the Agera crew until end of August.

agera-edc / DataSpaceConnector