Provider
Playground
The provider part of the TSG Playground consists out of two types of interactions:
- Providing artifacts
- Providing API endpoints
For providing resources to other connectors it is required that the connector is deployed in way that it is reachable from the internet. Therefore, the tutorials are focussed on Public Kubernetes deployments.
Providing artifacts
Providing artifacts is the default IDS way of interaction between two connectors. Following the general process of:
- uploading an artifact to your local connector including metadata and optionally a contract offer,
- publishing the metadata of the artifact to the metadata broker,
- perform (automatic) policy negotiation on receival of contract requests,
- providing the artifact.
The test connector deployed at https://test-connector.playground.dataspac.es/ui/ can be used as consumer for the artifact that is deployed on your connector.
Providing API endpoints
Providing API endpoints is an addition to the default IDS interaction that allows to exchange API endpoints. This allows for existing HTTP services to work over IDS. For this the OpenAPI Data App is used.
The process of providing an API is as follows:
- configure/deploy the backend service implementing an OpenAPI specification,
- publish the metadata of the service to the metadata broker,
- perform (automatic) policy negotiation on receival of contract requests,
- forward the request to the backend service,
- exchange the response to the request to the requestor.
The test connector deployed at https://test-connector.playground.dataspac.es/ui/ can be used as consumer for the artifact that is deployed on your connector.