Quick question before I spend too much time on thi...
# flyte-support
c
Quick question before I spend too much time on this -- is there a way to use
pyflyte
or
flytectl
with the HTTP REST API instead of GRPC API? I haven't been able to figure out how to set
admin.endpoint
properly to use the HTTP REST successfully. GRPC works fine when I use
kubectl
to forward port
8089
and set it
dns:///localhost:8089
.
> FlyteAdmin uses the grpc-gateway library to serve incoming gRPC and HTTP requests with identical handlers. I see the docs here mention that we should be able to handle both gRPC and HTTP requests so I'm trying to figure out how to configure the CLI to use HTTP instead.
c
I think grpc-gateway is mainly to support UI requests. pyflyte/flytectl can support HTTP 2.0 no problem so there is no point in using grpc-gateway. They will just natively use gRPC
You're just having issues getting
pyflyte
or
flytectl
to work/configured with the gRPC API?
c
I am interested in using the HTTP API instead of the GRPC API with the CLI I want to put an AWS API Gateway (only supports http 1.1) in front of the HTTP API and then contribute an aws sigv4 authentication method to use with pyflyte / flytectl to talk to the API Gateway
Any pointers on where to change the code for the python and go CLI to use HTTP API instead of GRPC?
g
I'm also curios, I understood that it's mandatory using GRPC, and unfortunately it's not possible to use only http.
c
You’d have to rewrite flytekit and flyectl, possibly using open API / swagger derived from the gateway annotated protos. There may be limitations as gRPC gateway doesn’t support everything in gRPC. Would not recommend
f
ya we would have to rewrite and its cumbersome, the reason why we added initially was to potentially support http OOB, but, this is a tall order
Just for all of you to know, we are Union are working on a V2, that does streamline a lot of the apis and then we would love a community effort that might support rest if desired. But, we are moving almost everything to buf connect