All Classes and Interfaces

Class
Description
Client for interacting with Apicurio Registry v3.
Raw content + content-type of an artifact in an ARBITRARY group (e.g.
 
Exception thrown when operations with Apicurio Registry fail.
Entity representing a configuration schema for a service.
 
Health check for services that platform-registration-service directly depends on.
One promotion awaiting the phase-2 git bake: a snapshot of the annotations that were written to the Apicurio system of record, queued for the (future) automation that turns them into a protos PR so the next build bakes them into descriptors.
Handles module registration operations.
Repository for managing service module registrations in PostgreSQL.
REST facade for module JSON config schemas (JSONForms / graph editor).
Creates the per-service module-work Kafka topic at module-registration time.
Produces events to Kafka for OpenSearch indexing.
 
 
 
 
 
Main platform registration service implementation.
Shared validation logic for RegisterRequest.
Defensive sanitizer for registration version strings coming from modules/services.
Retrieves module configuration schemas from the platform registry (DB, then Apicurio).
Handles service discovery and lookup operations.
Entity representing a registered service module in the system.
Handles service registration operations.
Status of a registered service module
Serves the descriptor door: resolves Any type_urls to self-contained descriptor sets and lists the available type catalog, mapping TypeDescriptorIndex results onto the documented gRPC error contract (INVALID_ARGUMENT / NOT_FOUND / FAILED_PRECONDITION).
In-memory index over the full-workspace protobuf descriptor snapshot baked into this service at build time (descriptors/pipestream-workspace.desc, a serialized DescriptorProtos.FileDescriptorSet produced by buf build over the entire pipestream-protos workspace).
One type's served descriptor set: the bytes, their content-hash version, and catalog metadata.
Catalog row for ListTypeDescriptors.
Serves the type metadata catalog doors, mapping TypeMetadataService results onto the documented gRPC error contract (NOT_FOUND unknown type / missing draft; INVALID_ARGUMENT bad scope combination or unknown field_path).
One writable metadata overlay: a (scope, graph, type) triple holding the field annotations for that layer.
Composite key: scope + graph + type.
The type metadata catalog: layered field annotations over message types.
Result of a promotion.
Result of a save.
Result of validating a RegisterRequest.