Is there way runn test of grpc with using "buf/validate/validate.proto" in proto ? about runn HOT 5 CLOSED

Hi @mztnnrt. Thank you for your report.

Currently, runn does not support the special behavior of buf.

Therefore import "buf/validate/validate.proto"; is treated the same as import "shared/shared.proto";

In other words, the solution is to create a buf/validate directory in the import path and put validate.proto flie there.

(I also use buf, so if this problem can be solved, it is an issue I would like to solve.)

from runn.

@k1LoW

Thanks for your reply ! we are helpful and glad to know the current status. 🙏
as you say, we noticed that there is the solution that import from local.

Already we tried based on your comment, it's work runn testing using validate.proto.

Thanks for your advice and reply, you can closed this issue anytime.

dir_located_buf_yaml = ./proto
buf export buf.build/bufbuild/protovalidate --path buf/validate --output $dir_located_buf_yaml

runn run ./e2e/backend/grpc.yaml --grpc-no-tls --grpc-import-path ./proto --grpc-proto ./proto/pingpb/service.proto
1 scenario, 0 skipped, 0 failures

from runn.

@mztnnrt
Hi.
We now support the Buf Schema Registry in v0.105.1.
You can use --grpc-buf-lock path/to/buf.lock to resolve buf/validate/validate.proto.

from runn.

Hi @k1LoW

Amazing ! We appreciate for your work !

Currently we tried --grpc-buf-lock flag, and working correctly 🙌
Thanks for it, we could remove the validate.proto which is pulled by manually, and we no longer need to manage.

Thanks so much ! 🙏

from runn.

Hi @mztnnrt.

Since V0.106.0, in many cases this can be resolved by simply specifying --grpc-buf-dir.

runn run ./e2e/backend/grpc.yaml --grpc-no-tls --grpc-buf-dir ./proto

Try it out 👍

from runn.