Registry record types are hard coded #107

Closed
opened 2023-08-25 12:45:12 +00:00 by dboreham · 1 comment
Owner

The types of records stored in the registry (e.g. service definitions, container images, npm packages) are currently defined in source code files here.

This is problematic because the definition of a new type will require a new binary to be built and released.

These type definitions should be defined as data, not in the binary, and able to be added at runtime.

The types of records stored in the registry (e.g. service definitions, container images, npm packages) are currently defined in source code files [here](https://github.com/cerc-io/laconicd/blob/a5681191a58f7709a6072d886802c4a5bb55919c/proto/vulcanize/registry/v1beta1/attributes.proto#L8). This is problematic because the definition of a new type will require a new binary to be built and released. These type definitions should be defined as data, not in the binary, and able to be added at runtime.
roysc self-assigned this 2023-10-11 20:08:06 +00:00

This issue is stale because it has been open 45 days with no activity. Remove Status: Stale label or comment or this will be closed in 7 days.

This issue is stale because it has been open 45 days with no activity. Remove `Status: Stale` label or comment or this will be closed in 7 days.
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/laconicd-deprecated#107
No description provided.