Currently, Hegel exposes both gRPC and HTTP APIs. The gRPC API exposes Get and Subscribe APIs. The HTTP API is predominantly composed of EC2 IMDSv1 plus an API for retrieving the current subscriptions (its unclear if this is used by consumers).
Consumers don't necessarily want both gRPC and HTTP endpoints exposed and likely only want to consume a particular standard like EC2 IMD or Equinix Metal metadata. This issue is to introduce flags for defining what technology should be exposed on launch.
The initial introduction of flags should enable all existing technologies by default with a view to swapping to opt-in in a future release.
Currently, Hegel exposes both gRPC and HTTP APIs. The gRPC API exposes
Get
andSubscribe
APIs. The HTTP API is predominantly composed of EC2 IMDSv1 plus an API for retrieving the current subscriptions (its unclear if this is used by consumers).Consumers don't necessarily want both gRPC and HTTP endpoints exposed and likely only want to consume a particular standard like EC2 IMD or Equinix Metal metadata. This issue is to introduce flags for defining what technology should be exposed on launch.
The initial introduction of flags should enable all existing technologies by default with a view to swapping to opt-in in a future release.