Python Client for Binary Authorization
Binary Authorization: The management interface for Binary Authorization, a service that provides policy-based deployment validation and control for images deployed to Google Kubernetes Engine (GKE), Anthos Service Mesh, Anthos Clusters, and Cloud Run.
Quick Start
In order to use this library, you first need to go through the following steps:
Installation
Install this library in a virtual environment using venv. venv is a tool that creates isolated Python environments. These isolated environments can have separate versions of Python packages, which allows you to isolate one project’s dependencies from the dependencies of other projects.
With venv, it’s possible to install this library without needing system install permissions, and without clashing with the installed system dependencies.
Code samples and snippets
Code samples and snippets live in the samples/ folder.
Supported Python Versions
Our client libraries are compatible with all current active and maintenance versions of Python.
Python >= 3.10, including 3.14
Unsupported Python Versions
Python <= 3.9
If you are using an end-of-life version of Python, we recommend that you update as soon as possible to an actively supported version.
Mac/Linux
python3 -m venv <your-env>
source <your-env>/bin/activate
pip install google-cloud-binary-authorizationWindows
py -m venv <your-env>
.\<your-env>\Scripts\activate
pip install google-cloud-binary-authorizationNext Steps
Read the Client Library Documentation for Binary Authorization to see other available methods on the client.
Read the Binary Authorization Product documentation to learn more about the product and see How-to Guides.
View this README to see the full list of Cloud APIs that we cover.
Logging
This library uses the standard Python logging functionality to log some RPC events that could be of interest for debugging and monitoring purposes.
Note the following:
Logs may contain sensitive information. Take care to restrict access to the logs if they are saved, whether it be on local storage or on Google Cloud Logging.
Google may refine the occurrence, level, and content of various log messages in this library without flagging such changes as breaking. Do not depend on immutability of the logging events.
By default, the logging events from this library are not handled. You must explicitly configure log handling using one of the mechanisms below.
Simple, environment-based configuration
To enable logging for this library without any changes in your code, set the GOOGLE_SDK_PYTHON_LOGGING_SCOPE environment variable to a valid Google
logging scope. This configures handling of logging events (at level logging.DEBUG or higher) from this library in a default manner, emitting the logged
messages in a structured format. It does not currently allow customizing the logging levels captured nor the handlers, formatters, etc. used for any logging
event.
A logging scope is a period-separated namespace that begins with google, identifying the Python module or package to log.
Valid logging scopes:
google,google.cloud.asset.v1,google.api,google.auth, etc.Invalid logging scopes:
foo,123, etc.
NOTE: If the logging scope is invalid, the library does not set up any logging handlers.
Environment-Based Examples
Enabling the default handler for all Google-based loggers
export GOOGLE_SDK_PYTHON_LOGGING_SCOPE=googleEnabling the default handler for a specific Google module (for a client library called
library_v1):
export GOOGLE_SDK_PYTHON_LOGGING_SCOPE=google.cloud.library_v1Advanced, code-based configuration
You can also configure a valid logging scope using Python’s standard logging mechanism.
Code-Based Examples
Configuring a handler for all Google-based loggers
import logging
from google.cloud import library_v1
base_logger = logging.getLogger("google")
base_logger.addHandler(logging.StreamHandler())
base_logger.setLevel(logging.DEBUG)Configuring a handler for a specific Google module (for a client library called
library_v1):
import logging
from google.cloud import library_v1
base_logger = logging.getLogger("google.cloud.library_v1")
base_logger.addHandler(logging.StreamHandler())
base_logger.setLevel(logging.DEBUG)Logging details
Regardless of which of the mechanisms above you use to configure logging for this library, by default logging events are not propagated up to the root logger from the google-level logger. If you need the events to be propagated to the root logger, you must explicitly set
logging.getLogger("google").propagate = Truein your code.You can mix the different logging configurations above for different Google modules. For example, you may want use a code-based logging configuration for one library, but decide you need to also set up environment-based logging configuration for another library.
If you attempt to use both code-based and environment-based configuration for the same module, the environment-based configuration will be ineffectual if the code -based configuration gets applied first.
The Google-specific logging configurations (default handlers for environment-based configuration; not propagating logging events to the root logger) get executed the first time any client library is instantiated in your application, and only if the affected loggers have not been previously configured. (This is the reason for 2.i. above.)
2 maintainers
Metadata
2 maintainers
Release files for google-cloud-binary-authorization 1.20.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| google_cloud_binary_authorization-1.20.0.tar.gz | 271.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| google_cloud_binary_authorization-1.20.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 528.9 kB
Release files / google_cloud_binary_authorization-1.20.0.tar.gz
| Download URL | google_cloud_binary_authorization-1.20.0.tar.gz |
|---|---|
| Size | 271.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b2fc81663b4f280c1a9a5e2f5134e3c53e5cf20c007b51344f672d141f3afdcf
|
|
BLAKE2b-256 checksum How to use checksums |
82eb4c3552d24b8e4d5a62e6e55372ef2a33eace35387607f3641fcab98c4df4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.2.0 CPython/3.11.2
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by Google Cloud, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / google_cloud_binary_authorization-1.20.0-py3-none-any.whl
| Download URL | google_cloud_binary_authorization-1.20.0-py3-none-any.whl |
|---|---|
| Size | 257.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
344b09b4a6c88fc340b2d8ec05a8e6649329ba2a05f735305a48034ad010776c
|
|
BLAKE2b-256 checksum How to use checksums |
1070e4cc94d05a66ed1e4754be924c25dc58c6815881df092fa101fb447f95e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.2.0 CPython/3.11.2
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by Google Cloud, verified by PyPI on Oct 1, 2026.
Transparency log
