Closed sgammon closed 2 years ago
Update: I've pushed the same support for grpcui
at fullstorydev/grpcui#188
I should also say, I'm happy to contribute a CI job, or Renovate config, etc., to reduce any potential maintenance burden in merging this. Thanks for such an awesome tool!
Hey there Fullstory,
I have no idea if this is useful for you guys, but I added Bazel support in a fork because we need it in our environment. It's a pretty conventional add with Gazelle, and should be maintainable along those lines as well. If there is any interest, I would be happy to contribute it back :)
Changes enclosed
rules_python
deps.bzl
To build/run with Bazel
There are two ways to build and run, the way things are set up with Gazelle. There is, the (1) build/run from source way (which you should use during development), and the (2) run from bindist way (which downstream Bazel codebases should use).
Provided for easy copy/paste:
Method 1: Local build/run
Method 2: Downstream run
First, the user adds the bindist to their own
WORKSPACE
, with:Then, they can run it in their own Bazel project easily with:
Support for method 2 is enclosed for Linux and macOS, although Windows would be relatively easy to add. All architectures are included that
grpcurl
is released for.