Question/Protobuf definitions about gpcloud-go HOT 6 CLOSED

We are focusing on the gRPC API, this is the source of truth (the protobuf-files). The REST API is a "byproduct" from the grpc-gateway, which will make the API accessible over REST. Because it's source is also the protobuf definitions, the REST API will always in line with the gRPC API. If the protobuf definitions change, both (REST and gRPC API) will change.

from gpcloud-go.

Sorry for the long delay on this.
You can dump the whole protobuf files with the buf export sub command like this (make sure you installed the buf tool):

$ buf export buf.build/gportal/gportal-cloud -o .

I've updated the README accordingly.
Alternative, you can pull it from here: https://github.com/G-PORTAL/gpcloud-proto

from gpcloud-go.

The protobuf definitions can be found here: https://buf.build/gportal/gportal-cloud/assets/main
For a quick reference, you can use the generated docs: https://buf.build/gportal/gportal-cloud
We are working on improving the documentation right now.

from gpcloud-go.

@f0086 amazing thank you, with these changes will there be changes to the rest api or is the main focus in gRPC

from gpcloud-go.

Is it possible to obtain the PB files from BSR remotely? Currently, only the definitions for Go and JS/TS clients are accessible through buf, and the assets on the BSR require authentication to access. If remote access to the PB files is not possible, could a mirror repository be created on Github or an alternative method be used for remote access?

from gpcloud-go.

Thanks all, appreciate it

from gpcloud-go.