Skip to content

Consistently name client interfaces #319

Closed
@invidian

Description

@invidian

Expected Behaviour

One can easily switch between working on code around workflows and templates and naming should follow the same convention, so interface names are not surprising, following POLA.

Current Behaviour

  • github.com/tinkerbell/tink/protos/workflow has WorkflowSvcClient
  • github.com/tinkerbell/tink/protos/hardware has HardwareServiceClient
  • github.com/tinkerbell/tink/protos/template has TemplateClient

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions