Skip to content

Avoid installing project specific binaries to system paths #153

@BulkBeing

Description

@BulkBeing

Currently we depend on 3 gRPC specific binaries: protoc-gen-go, protoc-gen-go-grpc and protoc.
We manage the version of protoc-gen-go and protoc-gen-go-grpc in the go.mod file. These binaries are installed if they doesn't already exist in the user's $PATH. If the user has a different version of this binary already installed, the version we specify in the go.mod will not be installed. This creates changes in the code generated from .proto files.

google.golang.org/grpc/cmd/protoc-gen-go-grpc v1.3.0

// - protoc-gen-go-grpc v1.4.0

I think we can install these binaries within a sub-directory of the numaflow-go (e.g., bin/) using the Makefile. The implementation should be easy - the GOBIN can be used to make go install binaries to a custom directory, and the protoc is available as a static binary.

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