Managing Cloud APIs and Libraries

You can access Google Cloud products and services from your code using Cloud APIs. These Cloud APIs expose a simple JSON REST interface that you can call via client libraries.

This document describes how to enable Cloud APIs and add Cloud Client Libraries to your project.

Note: For projects that don't use both Java and Maven, Cloud Code does not add the Cloud Client Libraries to your build automatically, but does support the other features described here and provides build snippets for your build system.

Browsing Cloud APIs

To explore all available Google Cloud APIs in your IDE, follow these steps:

1. Select Tools > Cloud Code > Cloud APIs.
2. Expand the Google Cloud APIs explorer tree to view all available APIs. The explorer groups Cloud APIs by category. You can also look for a specific API using the Search APIs search bar.

3. Click an API to view more details, such as its status, language-specific installation instructions for its corresponding client libraries, and relevant documentation.

Enabling Cloud APIs

To quickly enable Cloud APIs for a project using the API details, follow these steps:

1. In the Cloud API details view, choose a Google Cloud project that you'd like to enable the Cloud API for.
2. Click the Enable API button.

   Once the API has been enabled you'll see a message confirming this change.

Adding the Cloud Client Libraries

To add libraries to your project in IntelliJ, follow these steps:

For Java Maven projects

1. Select Tools > Cloud Code > Cloud APIs.

The Manage Google Cloud APIs dialog displays the supported libraries.


2. Select your preferred library type from the choice of Google Cloud Client Library (recommended) or Java Spring GCP Library.
3. In the Module drop-down menu, select the module that you want to add the library to.
Note: Google Cloud Java solves version conflicts between libraries by adding the Google Cloud Java Bill of Materials (BOM) to the pom.xml file of your projects.
4. Click Add Maven Dependency to add BOM and client library to your project.

For all other projects

1. Select Tools > Cloud Code > Cloud APIs.

The Manage Google Cloud APIs dialog displays the supported libraries.


2. Install the API using the installation instructions listed on the API details page for your preferred language.
   If you're developing a Java application, you need to also specify your library preference, Google Cloud Client Library (recommended) or Java Spring GCP Library.

Setting up authentication

After you've enabled the required APIs and added the necessary client libraries, you need to configure your application in order for it to be successfully authenticated. Your configuration depends on your type of development and the platform you're running on.

Once you complete the relevant authentication steps, your application can authenticate and is ready to be deployed.

Local development

Local machine

1. Cloud Code ensures you have your Application Default Credentials (ADC) set, if you logged into Google Cloud via your IDE.
   If you logged into Google Cloud outside your IDE (for example, via the gcloud command-line tool), you need to run gcloud auth login --update-adc to set your ADC. This also lets Google Cloud client libraries find your ADC to authenticate with.

minikube

1. Cloud Code ensures you have your Application Default Credentials (ADC) set, if you logged into Google Cloud via your IDE.
   If you logged into Google Cloud outside your IDE (for example, via the gcloud command-line tool), you need to run gcloud auth login --update-adc to set your ADC. This also lets minikube find your ADC to authenticate with.
2. Start minikube with minikube start --addons gcp-auth. This mounts your ADC in your pods. For a detailed minikube auth guide for Google Cloud, refer to the minikube gcp-auth docs.

Other local K8s clusters

1. Cloud Code ensures you have your Application Default Credentials (ADC) set, if you logged into Google Cloud via your IDE.
   If you logged into Google Cloud outside your IDE (for example, via the gcloud command-line tool), you need to run gcloud auth login --update-adc to set your ADC.
2. Mount your local gcloud directory in your Kubernetes pods by editing the Pod specification in the Pod or Deployment manifests, so that the Google Cloud Client Libraries can find your credentials. Kubernetes pod configuration example:

   apiVersion: v1
   kind: Pod
   metadata:
     name: my-app
     labels:
       name: my-app
   spec:
     containers:
     - name: my-app
       image: gcr.io/google-containers/busybox
       ports:
         - containerPort: 8080
       volumeMounts:
         - mountPath: /root/.config/gcloud
           name: gcloud-volume
     volumes:
       - name: gcloud-volume
         hostPath:
           path: /path/to/home/.config/gcloud

Cloud Run

1. Cloud Code ensures you have your Application Default Credentials (ADC) set, if you logged into Google Cloud via your IDE.
   If you logged into Google Cloud outside your IDE (for example, using the gcloud command-line tool), you need to run gcloud auth login --update-adc to set your ADC. This also lets the Cloud Run local simulated environment find your ADC to authenticate with.

Remote development

Google Kubernetes Engine

Depending on the scope of your project, you can choose how you authenticate Google Cloud services on GKE:

• (Development only)
  Note: GKE cluster service account and access scope settings are permanent; once your cluster is created, these settings cannot be changed. Specify the settings as recommended below.
  1. Create a GKE cluster with the following settings:
     • Ensure you're using the service account GKE uses by default, the Compute Engine default service account, and that Access scopes is set at Allow full access to all Cloud APIs (both settings accessible in the Node Pools > Security section).
       Since the Compute Engine service account is shared by all workloads deployed on your node, this method overprovisions permissions and should only be used for development.
     • Ensure Workload Identity is not enabled on your cluster (in the Cluster > Security section).
  2. Assign the necessary roles to the Compute Engine default service account:
     • If you're trying to access a secret, follow these Secret Manager-specific steps to set up the required roles on your service account.
     • If the Compute Engine default service account is being used, the correct IAM roles may already be applied.

     • For a list of IAM role types and predefined roles you can grant to identities, see the Understanding roles guide.

       For steps to grant the roles, see Granting, changing, and revoking access to resources.

• (Recommended for production)
  1. Configure your GKE cluster and application with Workload Identity to authenticate Google Cloud services on GKE. This associates your Kubernetes service account with your Google service account.
  2. Configure your Kubernetes Deployment to reference the Kubernetes service account by setting the .spec.serviceAccountName field in your Kubernetes Deployment YAML file.
     If you're working on an app created from a Cloud Code template, this file is located under the kubernetes-manifests folder.
  3. If the Google Cloud service you're trying to access requires additional roles, grant them for the Google service account you're using to develop your app:
     • If you're trying to access a secret, follow these Secret Manager-specific steps to set up the required roles on your service account.

     • For a list of IAM role types and predefined roles you can grant to identities, see the Understanding roles guide.

       For steps to grant the roles, see Granting, changing, and revoking access to resources.

Cloud Run

1. To create a new unique service account for deploying your Cloud Run application, on the Service Accounts page, select the project that your secret is stored in.

   Go to the Service Accounts page

2. Click Create service account.
3. In the Create service account dialog, enter a descriptive name for the service account.
4. Change the Service account ID to a unique, recognizable value and then click Create.
5. If the Google Cloud service you're trying to access requires additional roles, grant them, click Continue, and then click Done.
6. To add your Kubernetes service account to your deploy configuration, navigate to your Cloud Run: Deploy run configuration, expand the Advanced revision settings section, and then specify your service account in the Service Account field.
   

Cloud Run

Depending on the scope of your project, you can choose how you authenticate Google Cloud services on GKE:

• (Development only)
  Note: GKE cluster service account and access scope settings are permanent; once your cluster is created, these settings cannot be changed. Specify the settings as recommended below.
  1. Create a GKE cluster with the following settings:
     • Ensure you're using the service account GKE uses by default, the Compute Engine default service account, and that Access scopes is set at Allow full access to all Cloud APIs (both settings accessible in the Node Pools > Security section).
       Since the Compute Engine service account is shared by all workloads deployed on your node, this method overprovisions permissions and should only be used for development.
       
     • Ensure Workload Identity is not enabled on your cluster (in the Cluster > Security section).
  2. Assign the necessary roles to the Compute Engine default service account:
     • If you're trying to access a secret, follow these Secret Manager-specific steps to set up the required roles on your service account.
     • If the Compute Engine default service account is being used, the correct IAM roles may already be applied.

     • For a list of IAM role types and predefined roles you can grant to identities, see the Understanding roles guide.

       For steps to grant the roles, see Granting, changing, and revoking access to resources.

• (Recommended for production)
  1. Configure your GKE cluster and application with Workload Identity to authenticate Google Cloud services on GKE. This associates your Kubernetes service account with your Google service account.
  2. To add your Kubernetes service account to your deploy configuration, navigate to your Cloud Run:Deploy run configuration, expand the Advanced revision settings section, and then specify your Kubernetes service account in the Service Account field.
     
  3. If the Google Cloud service you're trying to access requires additional roles, grant them for the Google service account you're using to develop your app:
     • If you're trying to access a secret, follow these Secret Manager-specific steps to set up the required roles on your service account.

     • For a list of IAM role types and predefined roles you can grant to identities, see the Understanding roles guide.

       For steps to grant the roles, see Granting, changing, and revoking access to resources.

Remote development with Secret Manager permissions enabled

If you're developing remotely, using a service account for authentication, and your application uses secrets, you need to complete a few more steps in addition to the remote development instructions. These steps assign your Google service account the role required to access a particular Secret Manager secret:

1. Open the Secret Manager panel by clicking the Secret Manager tab in the right Cloud Code sidebar.

2. Select the secret that you want to access in your code.

3. Switch to the Permissions tab and then configure your secret's permissions by clicking Edit Permission. The Secret Manager configuration page for the secret opens in your web browser.

   

4. In Cloud Console, click Show Info Panel and then click Add principal.

5. Assign your service account the Secret Manager Secret Accessor role.

   Your service account has permission to access this secret.

Getting support

To submit feedback or report an issue in your IntelliJ IDE, go to Tools > Cloud Code > Help / About > Submit feedback or report an issue to report an issue on GitHub, or ask a question on Stack Overflow.

You can also join the #cloud-code channel, which is part of the Google Cloud Slack community.