Introduce a new usesEndpoints property in a service that will be used to generate a list and diagram of endpoints of other services used by this service. The 1st level will be the name of the service it will call and the 2nd level will describe the OpenAPI "operationId".
operationId is an optional unique string used to identify an operation. If provided, these IDs must be unique among all operations described in your API.
I assume this is relatively easy to build because it just adds a new two level deep array to the already existing service data. So it would require just some data transformation and extraction from the schema to output the data for d3.js hat then could visualize it in a widget on the service page.
Motivation
We want to understand and visualize our existing HTTP API calls between services.
Have you read the Contributing Guidelines on issues?
Description
Introduce a new
usesEndpointsproperty in a service that will be used to generate a list and diagram of endpoints of other services used by this service. The 1st level will be the name of the service it will call and the 2nd level will describe the OpenAPI "operationId".Part of the service description:
Ideally we could also render a map of all cross references between services, a complete map, similar to this https://observablehq.com/@d3/force-directed-tree?intent=fork when viewing a service page.
I assume this is relatively easy to build because it just adds a new two level deep array to the already existing service data. So it would require just some data transformation and extraction from the schema to output the data for d3.js hat then could visualize it in a widget on the service page.
Motivation
We want to understand and visualize our existing HTTP API calls between services.