Skip to content

Introduction

Services wants to register their information (e.g., API endpoints) which can be searched/discovered by other services that want to consume the information. Service registry should be available before any other app/service installed on IED, hence it is integrated with IED runtime.

  • The existing service registry is enabled with the HTTP REST interface for supporting maximum use cases.
  • Free-form Schema Info will enable any service to register with any type of schema info. Free-from is a JSON format and it will be enabled to search using JEMSPath query. For more details refer: https://jmespath.org/
  • The user provided metadata(details of the app) will be merged to detail.json file which is already generated by the publisher. The application is installed on IED and all the information related to app will be available in service registry. Any application can request for information on other application installed on IED via service registry using API.

  • Users can provide metadata through the App Publisher, and using the unique application ID, the same data can be updated via the HTTP PUT API. This approach does not work with gRPC, as there is no synchronization between the App Publisher and gRPC.

    alt text

How to access Service Registry API

Install IED and all the application registered on IED there data will be available via API

Servers

Authorization

IED: Authorization is required before using the Service Registry API's via IED. You need to use authorization token before using the API.

For more details on Authentication and Authorization please refer:SPIFFE ID