Lack of support for insecure tls

[Aran Wilkinson]

Describe the bug

I've been trying to use evans with a insecure tls connection but it seems like it does not work as expected

I've been able to validate this using another tool https://github.com/fullstorydev/grpcurl which does support insecure tls

To reproduce

Using grpcurl

-> grpcurl -insecure localhost:9090 list
grpc.reflection.v1alpha.ServerReflection

With evans

✗ evans --host localhost --port 9090 -r repl
evans: failed to run REPL mode: failed to instantiate a new spec: failed to instantiate the spec: failed to list packages by gRPC reflection: failed to list services from reflection enabled gRPC server: rpc error: code = Unavailable desc = connection closed

Expected behavior

I expected a --insecure flag that would put the gRPC connection into insecure tls mode

Screenshots

n/a

Environment

n/a

Additional context

n/a

[ktr]

Evans tries to request to the destination server through an insecure connection by default.
Could you provide more described information about your server (e.g. a minimum Dockerfile that reproduces the behavior)?

[no-response]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.