#google #protocols #web #google-api #binaryauthorization #web-api #api-bindings


A complete library to interact with Binary Authorization (protocol v1beta1)

16 stable releases (4 major)

5.0.3+20230113 Aug 23, 2023
5.0.2+20230113 Mar 16, 2023
5.0.2-beta-1+20230113 Jan 25, 2023
4.0.1+20220225 Sep 14, 2022
1.0.8+20181005 Oct 14, 2018

#2732 in Web programming

Download history 1/week @ 2024-03-08 2/week @ 2024-03-15 119/week @ 2024-03-29 23/week @ 2024-04-05

193 downloads per month
Used in google-binaryauthorizatio…

MIT license


The google-binaryauthorization1_beta1 library allows access to all features of the Google Binary Authorization service.

This documentation was generated from Binary Authorization crate version 5.0.3+20230113, where 20230113 is the exact revision of the binaryauthorization:v1beta1 schema built by the mako code generator v5.0.3.

Everything else about the Binary Authorization v1_beta1 API can be found at the official documentation site.


Handle the following Resources with ease from the central hub ...

Structure of this Library

The API is structured into the following primary items:

  • Hub
    • a central object to maintain state and allow accessing all Activities
    • creates Method Builders which in turn allow access to individual Call Builders
  • Resources
    • primary types that you can apply Activities to
    • a collection of properties and Parts
    • Parts
      • a collection of properties
      • never directly used in Activities
  • Activities
    • operations to apply to Resources

All structures are marked with applicable traits to further categorize them and ease browsing.

Generally speaking, you can invoke Activities like this:

let r = hub.resource().activity(...).doit().await

Or specifically ...

let r = hub.projects().attestors_get_iam_policy(...).doit().await
let r = hub.projects().attestors_set_iam_policy(...).doit().await
let r = hub.projects().policy_get_iam_policy(...).doit().await
let r = hub.projects().policy_set_iam_policy(...).doit().await

The resource() and activity(...) calls create builders. The second one dealing with Activities supports various methods to configure the impending operation (not shown here). It is made such that all required arguments have to be specified right away (i.e. (...)), whereas all optional ones can be build up as desired. The doit() method performs the actual communication with the server and returns the respective result.


Setting up your Project

To use this library, you would put the following lines into your Cargo.toml file:

google-binaryauthorization1_beta1 = "*"
serde = "^1.0"
serde_json = "^1.0"

A complete example

extern crate hyper;
extern crate hyper_rustls;
extern crate google_binaryauthorization1_beta1 as binaryauthorization1_beta1;
use binaryauthorization1_beta1::{Result, Error};
use std::default::Default;
use binaryauthorization1_beta1::{BinaryAuthorization, oauth2, hyper, hyper_rustls, chrono, FieldMask};

// Get an ApplicationSecret instance by some means. It contains the `client_id` and 
// `client_secret`, among other things.
let secret: oauth2::ApplicationSecret = Default::default();
// Instantiate the authenticator. It will choose a suitable authentication flow for you, 
// unless you replace  `None` with the desired Flow.
// Provide your own `AuthenticatorDelegate` to adjust the way it operates and get feedback about 
// what's going on. You probably want to bring in your own `TokenStorage` to persist tokens and
// retrieve them from storage.
let auth = oauth2::InstalledFlowAuthenticator::builder(
let mut hub = BinaryAuthorization::new(hyper::Client::builder().build(hyper_rustls::HttpsConnectorBuilder::new().with_native_roots().https_or_http().enable_http1().build()), auth);
// You can configure optional parameters by calling the respective setters at will, and
// execute the final call using `doit()`.
// Values shown here are possibly random and not representative !
let result = hub.projects().attestors_get_iam_policy("resource")

match result {
    Err(e) => match e {
        // The Error enum provides details about what exactly happened.
        // You can also just use its `Debug`, `Display` or `Error` traits
        |Error::UploadSizeLimitExceeded(_, _)
        |Error::JsonDecodeError(_, _) => println!("{}", e),
    Ok(res) => println!("Success: {:?}", res),

Handling Errors

All errors produced by the system are provided either as Result enumeration as return value of the doit() methods, or handed as possibly intermediate results to either the Hub Delegate, or the Authenticator Delegate.

When delegates handle errors or intermediate values, they may have a chance to instruct the system to retry. This makes the system potentially resilient to all kinds of errors.

Uploads and Downloads

If a method supports downloads, the response body, which is part of the Result, should be read by you to obtain the media. If such a method also supports a Response Result, it will return that by default. You can see it as meta-data for the actual media. To trigger a media download, you will have to set up the builder by making this call: .param("alt", "media").

Methods supporting uploads can do so using up to 2 different protocols: simple and resumable. The distinctiveness of each is represented by customized doit(...) methods, which are then named upload(...) and upload_resumable(...) respectively.

Customization and Callbacks

You may alter the way an doit() method is called by providing a delegate to the Method Builder before making the final doit() call. Respective methods will be called to provide progress information, as well as determine whether the system should retry on failure.

The delegate trait is default-implemented, allowing you to customize it with minimal effort.

Optional Parts in Server-Requests

All structures provided by this library are made to be encodable and decodable via json. Optionals are used to indicate that partial requests are responses are valid. Most optionals are are considered Parts which are identifiable by name, which will be sent to the server to indicate either the set parts of the request or the desired parts in the response.

Builder Arguments

Using method builders, you are able to prepare an action call by repeatedly calling it's methods. These will always take a single argument, for which the following statements are true.

Arguments will always be copied or cloned into the builder, to make them independent of their original life times.


The binaryauthorization1_beta1 library was generated by Sebastian Thiel, and is placed under the MIT license. You can read the full text at the repository's license file.


~537K SLoC