googleapis-raw

These are raw bindings for Google APIs based on grpcio.

Version notes

This library is currently locked to grpcio 0.12.0 and protobuf 2.28.0. This is due to an internal dependency of grpcio. Be sure that you match these library versions in your library or application.

Documentation

To generate and open documentation, run:

sh cargo doc --open

Examples

To run hand-written examples, try:

sh cargo run --example spanner-query cargo run --example bigtable-query

Setting up Google Cloud SDK

Before running examples, make sure the Google Cloud SDK is set up in your environment. If you need help, follow these guides:

As a final check:

Run gcloud info to see the SDK configuration.
Run echo $GOOGLE_APPLICATION_CREDENTIALS to verify that the credentials have been set up.
Run gcloud auth login to login into Google Cloud

There is Docker setup available that installs all necessary tools, libraries, see the README inside the ./docker folder.

Useful links for setting up specific Google services:

Generating Rust bindings from `.proto` files

NOTE: You may need to update these bindings after protobuf updates. The process requires an update to the protobuf-codegen cargo plugin.

This requires the installation of protobuf library and protoc-gen-rust, a plugin for protobuf. The installed protobuf version and the protobuf crate should have the same version, e.g. 2.7.0. Installation of the protoc-gen-rust plugin is done via cargo:

sh cargo install protobuf-codegen

Make sure the protoc-gen-rust binary is available in your $PATH env variable.

Then:

1) In the ./src directory, remove all the *.rs that are not mod.rs [1]. You may wish to run the prepare.sh script.

2) Run the ./generate.sh script

ensure that a proper build works by running cargo build.

[1] The generate.sh script will NOT generate the required mod.rs files for the directories. In addition, the generated rust modules will look for several modules that are super to their package. protoc may not overwrite an existing, generated rust file which could lead to complications. It's easiest if you simily leave the mod.rs files in place and remove the other rust files, or copy the mod.rs files from a backup. Running a cargo build will definitely identify the modules that may be missing and that you'll have to add via a line like:

rust pub(crate) use crate::{ empty, iam::v1::{iam_policy, policy}, longrunning::operations, };

(which was taken from src/rpc/spanner/admin/instance/v1/mod.rs)

Please note that the source grpc repo may contiain one or more older submodule references that may need to be updated (e.g. .grpc/third_party/googleapis). This may require manual updating as well as manunal updating/correction of the various, mod.rs files. Pay close attention to interdependencies. These may need to be specified in the directory mods (see .src/storage/v1/mod.rs for an example. Remember, you can use the r# prefix in rust to except a reserved name for use, e.g. use mod crate::r#type)

When Updating

Remember to update the dependent submodules by calling

git submodule update --init --recursive

NOTE: this may alter the pre-generated mod files requiring old modules to be dropped or new modules to be added. Ensure that the various mod.rs files capture these changes.

Google Cloud Console

Links to Google Cloud Console for our testing environment:

References

Google APIs and their .proto files:

Golang clients: