Use Registration Service API to seed federated catalog of all participant EDC instances.
The deployment pipeline deploys one instance of Registration Service in MVD set up. The Registration Service instance is configured to use json files as a data source and exposes the data via REST API.
The deployment pipeline for each participant creates a file in common folder in a file share, with a prefix corresponding to each unique deployment. For example, when deploying participants company1
and company2
, the files could be named:
280-company1.json
280-company2.json
Here 280-
is an arbitrary prefix for one dataspace (in continuous delivery, one deployment).
Each file contains a serialized EDC FederatedCacheNode
object, for example:
{
"name": "company1",
"supportedProtocols": [
"ids-multipart"
],
"url": "http://280-company1-edc-mvd.northeurope.azurecontainer.io:8282"
}
URLs of deployed EDC instances are only known after deployment in parallel Terraform runs.
Until the federated catalog node list can be dynamically updated, this requires restarting the connectors after all catalog files have been stored.