Google Cloud Java Client Libraries

Java idiomatic client for Google Cloud Platform services.

• Java on Google Cloud

Supported APIs

Libraries are available on GitHub and Maven Central for developing Java applications that interact with individual Google Cloud services:, Client, Release Level, Version, ------, -------------, -------, BigQuery, , , Cloud AutoML, , , Cloud Bigtable, , , Cloud Build, , , Cloud Datastore, , , Cloud Data Loss Prevention, , , Cloud Firestore, , , Cloud KMS, , , Cloud Natural Language, , , Cloud Pub/Sub, , , Cloud Scheduler, , , Cloud Spanner, , , Cloud Speech, , , Cloud Storage, , , Cloud Translation, , , Cloud Tasks, , , Cloud Text-to-Speech, , , Cloud Video Intelligence, , , Cloud Vision, , , Stackdriver Logging, , , Stackdriver Monitoring, , , Stackdriver Trace, , , BigQuery Data Transfer, , , BigQuery Storage, , , Cloud Asset, , , Cloud Billing Budgets, , , Cloud Container Analysis, , , Cloud Dataproc, , , Cloud Data Catalog, , , Cloud Data Labeling, , , Cloud IAM Service Account Credentials API, , , Cloud IoT Core, , , Cloud Memorystore for Redis, , , Cloud OS Login, , , Cloud Phishing Protection, , , Cloud Recommender, , , Cloud Secret Manager, , , Cloud Security Center, , , Cloud Security Scanner, , , Cloud Talent Solution, , , Cloud Web Risk, , , Dialogflow, , , Kubernetes Engine, , , reCAPTCHA Enterprise, , , Stackdriver Error Reporting, , , Cloud Compute, , , Cloud DNS, , , Cloud Logging via Logback, , , Cloud Resource Manager, , , Cloud Storage via NIO, , , If the service is not listed, google-api-java-client interfaces with additional Google Cloud APIs using a legacy REST interface.

When building Java applications, preference should be given to the libraries listed in the table.

Quickstart

To call any of the supported Google Cloud Services simply add a corresponding client library
artifact as a dependency to your project. The following instructions use google-cloud-storage
as an example (specific instructions can be found in the README of each client).

If you are using Maven, add this to your pom.xml file:

<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>com.google.cloud</groupId>
      <artifactId>libraries-bom</artifactId>
      <version>3.4.0</version>
      <type>pom</type>
      <scope>import</scope>
     </dependency>
   </dependencies>
</dependencyManagement>

<dependencies>
  <dependency>
    <groupId>com.google.cloud</groupId>
    <artifactId>google-cloud-storage</artifactId>
  </dependency>
  ...

If you are using Gradle, add this to your dependencies

compile 'com.google.cloud:google-cloud-storage:1.102.0'

If you are using SBT, add this to your dependencies

libraryDependencies += "com.google.cloud" % "google-cloud-storage" % "1.102.0"

If you're using IntelliJ or Eclipse, you can add client libraries to your project using these IDE plugins:

• Cloud Tools for IntelliJ
• Cloud Tools for Eclipse

Besides adding client libraries, the plugins provide additional functionality, such as service account key management. Refer to the documentation for each plugin for more details.

These client libraries can be used on App Engine standard for Java 8 runtime and App Engine flexible (including the Compat runtime). Most of the libraries do not work on the App Engine standard for Java 7 runtime. However, Datastore, Storage, and Bigquery should work.

Specifying a Project ID

Most google-cloud libraries require a project ID. There are multiple ways to specify this project ID.

1. When using google-cloud libraries from within Compute/App Engine, there's no need to specify a project ID. It is automatically inferred from the production environment.
2. When using google-cloud elsewhere, you can do one of the following:

• Supply the project ID when building the service options. For example, to use Datastore from a project with ID "PROJECT_ID", you can write:

Datastore datastore = DatastoreOptions.newBuilder().setProjectId("PROJECT_ID").build().getService();

• Specify the environment variable GOOGLE_CLOUD_PROJECT to be your desired project ID.
• Set the project ID using the Google Cloud SDK. To use the SDK, download the SDK if you haven't already, and set the project ID from the command line. For example:

gcloud config set project PROJECT_ID

google-cloud determines the project ID from the following sources in the listed order, stopping once it finds a value:

1. The project ID supplied when building the service options
2. Project ID specified by the environment variable GOOGLE_CLOUD_PROJECT
3. The App Engine / Compute Engine project ID
4. The project ID specified in the JSON credentials file pointed by the GOOGLE_APPLICATION_CREDENTIALS environment variable
5. The Google Cloud SDK project ID

In cases where the library may expect a project ID explicitly, we provide a helper that can provide the inferred project ID:

  import com.google.cloud.ServiceOptions;
  ...
  String projectId = ServiceOptions.getDefaultProjectId();

Authentication

google-cloud-java uses
https://github.com/googleapis/google-auth-library-java
to authenticate requests. google-auth-library-java supports a wide range of authentication types;
see the project's README
and javadoc for more
details.

To access Google Cloud services, you first need to ensure that the necessary Google Cloud APIs are
enabled for your project. To do this, follow the instructions on the
authentication document
shared by all the Google Cloud language libraries.

Next, choose a method for authenticating API requests from within your project:

1. When using google-cloud libraries from within Compute/App Engine, no additional authentication
   steps are necessary. For example:

Storage storage = StorageOptions.getDefaultInstance().getService();

2. When using google-cloud libraries elsewhere, there are several options:

• Generate a JSON service account key.
  After downloading that key, you must do one of the following:
  • Define the environment variable GOOGLE_APPLICATION_CREDENTIALS to be the location of the key.
    For example:

  export GOOGLE_APPLICATION_CREDENTIALS=/path/to/my/key.json
  

  • Supply the JSON credentials file when building the service options. For example, this Storage
    object has the necessary permissions to interact with your Google Cloud Storage data:

  Storage storage = StorageOptions.newBuilder()
      .setCredentials(ServiceAccountCredentials.fromStream(new FileInputStream("/path/to/my/key.json")))
      .build()
      .getService();
  

• If running locally for development/testing, you can use the
  Google Cloud SDK. Create Application Default Credentials with
  gcloud auth application-default login, and then google-cloud will automatically detect such
  credentials.
• If you already have an OAuth2 access token, you can use it to authenticate (notice that in this
  case, the access token will not be automatically refreshed):

Storage storage = StorageOptions.newBuilder()
    .setCredentials(GoogleCredentials.create(new AccessToken(accessToken, expirationTime)))
    .build()
    .getService();

If no credentials are provided, google-cloud will attempt to detect them from the environment
using GoogleCredentials.getApplicationDefault() which will search for Application Default
Credentials in the following locations (in order):

1. The credentials file pointed to by the GOOGLE_APPLICATION_CREDENTIALS environment variable
2. Credentials provided by the Google Cloud SDK gcloud auth application-default login command
3. Google App Engine built-in credentials
4. Google Cloud Shell built-in credentials
5. Google Compute Engine built-in credentials

Troubleshooting

To get help, follow the instructions in the Troubleshooting document.

Using a proxy

Clients in this repository use either HTTP or gRPC for the transport layer.
The README of each client documents the transport layer the client uses.

For HTTP clients, a proxy can be configured by using http.proxyHost and
related system properties as documented by
Java Networking and Proxies.

For gRPC clients, a proxy can be configured by using the
GRPC_PROXY_EXP environment variable as documented by
the gRPC release notes.
Please note that gRPC proxy support is currently experimental.

Java Versions

Java 7 or above is required for using the clients in this repository.

Supported Platforms

Clients in this repository use either HTTP or gRPC for the transport layer. All
HTTP-based clients should work in all environments.

For clients that use gRPC, the supported platforms are constrained by the platforms
that Forked Tomcat Native supports,
which for architectures means only x86_64, and for operating systems means Mac OS X,
Windows, and Linux. Additionally, gRPC constrains the use of platforms with
threading restrictions.

Thus, the following are not supported:

• Android
  • Consider Firebase, which includes many of these APIs.
  • It is possible to use these libraries in many cases, although it is unsupported.
    You can find examples, such as this one,
    in this example repository but consider the risks carefully before using these libraries in an application.
• Alpine Linux (due to netty-tcnative requiring glibc, which is not present on Alpine)
• Raspberry Pi (since it runs on the ARM architecture)
• Google App Engine Standard Java 7

The following environments should work (among others):

• standalone Windows on x86_64
• standalone Mac OS X on x86_64
• standalone Linux on x86_64
• Google Compute Engine (GCE)
• Google Container Engine (GKE)
• Google App Engine Standard Java 8 (GAE Std J8)
• Google App Engine Flex (GAE Flex)

Testing

This library provides tools to help write tests for code that uses google-cloud services.

See TESTING to read more about using our testing helpers.

Versioning

This library follows Semantic Versioning, with some
additional qualifications:

1. Components marked with @BetaApi are considered to be "0.x" features inside
   a "1.x" library. This means they can change between minor and patch releases
   in incompatible ways. These features should not be used by any library "B"
   that itself has consumers, unless the components of library B that use
   @BetaApi features are also marked with @BetaApi. Features marked as
   @BetaApi are on a path to eventually become "1.x" features with the marker
   removed.

   Special exception for google-cloud-java: google-cloud-java is
   allowed to depend on @BetaApi features in gax-java without declaring the consuming
   code @BetaApi, because gax-java and google-cloud-java move in step
   with each other. For this reason, gax-java should not be used
   independently of google-cloud-java.

2. Components marked with @InternalApi are technically public, but only
   because of the limitations of Java's access
   modifiers. For the purposes of semver, they should be considered private.

Please note it is currently under active development. Any release versioned 0.x.y is
subject to backwards incompatible changes at any time.

GA

Libraries defined at a GA quality level are expected to be stable and all updates in the
libraries are guaranteed to be backwards-compatible. Any backwards-incompatible changes will lead
to the major version increment (1.x.y -> 2.0.0).

Beta

Libraries defined at a Beta quality level are expected to be mostly stable and
we're working towards their release candidate. We will address issues and requests with
a higher priority.

Alpha

Libraries defined at an Alpha quality level are still a work-in-progress and
are more likely to get backwards-incompatible updates. Additionally, it's possible for Alpha
libraries to get deprecated and deleted before ever being promoted to Beta or GA.

Contributing

Contributions to this library are always welcome and highly encouraged.

See google-cloud's CONTRIBUTING documentation and the shared documentation for more information on how to get started.

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms. See Code of Conduct for more information.

License

Apache 2.0 - See LICENSE for more information.