Skip to content

[chore]: Autogenerated DTO with protobuff #217

Open

Description

@SuvabrataChowdhury

Chore Description

Currently the Data Transfer Objects are manually defined by the service. Example PipelineBuildDTO .

When new services are introduced these will need to define it's own DTO with the same schema which can introduce drifting of these core definitions.

Solution is to introduce gRPC's .proto definitions for these DTOs and the respective services will autogenerate the codes just like how the UI client is autogenerating client side code from OpenAPI specs.

Benefit hypothesis

Ensure any and all services conform to the same communication schema.

Chore importance

High

Additional comments

No response

Metadata

Metadata

Assignees

Labels

choreSome tasks, other than core application development, which helps the application's development.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions