Skip to content


Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.

Google Resource Manager API Client for Java

Java idiomatic client for Resource Manager API.

Maven Stability


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



If you are using Maven without BOM, add this to your dependencies:


If you are using Gradle 5.x or later, add this to your dependencies

implementation platform('')

implementation ''

If you are using Gradle without BOM, add this to your dependencies

implementation ''

If you are using SBT, add this to your dependencies

libraryDependencies += "" % "google-cloud-resourcemanager" % "1.4.0"


See the Authentication section in the base directory's README.


The client application making API calls must be granted authorization scopes required for the desired Resource Manager API APIs, and the authenticated principal must have the IAM role(s) required to access GCP resources using the Resource Manager API API calls.

Getting Started


You will need a Google Cloud Platform Console project with the Resource Manager API API enabled.

Follow these instructions to get your project set up. You will also need to set up the local development environment by installing the Google Cloud SDK and running the following commands in command line: gcloud auth login and gcloud config set project [YOUR PROJECT ID].

Installation and setup

You'll need to obtain the google-cloud-resourcemanager library. See the Quickstart section to add google-cloud-resourcemanager as a dependency in your code.

About Resource Manager API

Resource Manager API enables you to programmatically manage resources by project, folder, and organization.

See the Resource Manager API client library docs to learn how to use this Resource Manager API Client Library.

Creating an authorized service object

To make authenticated requests to Google Cloud Resource Manager, you must create a service object with Google Cloud SDK credentials. You can then make API calls by calling methods on the Resource Manager service object. The simplest way to authenticate is to use Application Default Credentials. These credentials are automatically inferred from your environment, so you only need the following code to create your service object:


ResourceManager resourceManager = ResourceManagerOptions.getDefaultInstance().getService();

Getting a specific project

You can load a project if you know its project ID and have read permissions to the project. To get a project, add the following import at the top of your file:


Then use the following code to get the project:

String projectId = "my-globally-unique-project-id"; // Change to a unique project ID
Project project = resourceManager.get(projectId);

Creating a project

All you need to create a project is a globally unique project ID. You can also optionally attach a non-unique name and labels to your project. Read more about naming guidelines for project IDs, names, and labels here. To create a project, add the following imports at the top of your file:


Then add the following code to create a project (be sure to change projectId to your own unique project ID).

String projectId = "my-globally-unique-project-id"; // Change to a unique project ID
Project project = resourceManager.create(ProjectInfo.newBuilder(projectId).build());

Note that the return value from create is a Project that includes additional read-only information, like creation time, project number, and lifecycle state. Read more about these fields on the Projects page. Project, a subclass of ProjectInfo, adds a layer of service-related functionality over ProjectInfo.

Editing a project

To edit a project, create a new ProjectInfo object and pass it in to the Project.replace method. For example, to add a label to a project to denote that it's launch status is "in development", add the following code:

Project newProject = project.toBuilder()
    .addLabel("launch-status", "in-development")

Note that the values of the project you pass in to replace overwrite the server's values for non-read-only fields, namely projectName and labels. For example, if you create a project with projectName "some-project-name" and subsequently call replace using a ProjectInfo object that didn't set the projectName, then the server will unset the project's name. The server ignores any attempted changes to the read-only fields projectNumber, lifecycleState, and createTime. The projectId cannot change.

Listing all projects

Suppose that we want a list of all projects for which we have read permissions. Add the following import:

import java.util.Iterator;

Then add the following code to print a list of projects you can view:

Iterator<Project> projectIterator = resourceManager.list().iterateAll().iterator();
System.out.println("Projects I can view:");
while (projectIterator.hasNext()) {

Managing IAM Policies

You can edit Google Cloud IAM (Identity and Access Management) policies on the project-level using this library as well. We recommend using the read-modify-write pattern to make policy changes. This entails reading the project's current policy, updating it locally, and then sending the modified policy for writing, as shown in the snippet below. First, add these imports:


Assuming you have completed the steps above to create the ResourceManager service object and load a project from the server, you just need to add the following code:

// Get the project's policy
Policy policy = project.getPolicy();

// Add a viewer
Policy.Builder modifiedPolicy = policy.toBuilder();
Identity newViewer = Identity.user("<insert user's email address here>");
modifiedPolicy.addIdentity(Role.viewer(), newViewer);

// Write policy
Policy updatedPolicy = project.replacePolicy(;

Note that the policy you pass in to replacePolicy overwrites the original policy. For example, if the original policy has two bindings and you call replacePolicy with a new policy containing only one binding, the two original bindings are lost.

Complete source code

We put together all the code shown above into three programs. The programs assume that you are running from your own desktop and used the Google Cloud SDK to authenticate yourself.

The first program creates a project if it does not exist. Complete source code can be found at

The second program updates a project if it exists and lists all projects the user has permission to view. Complete source code can be found at

The third program modifies the IAM policy associated with a project using the read-modify-write pattern. Complete source code can be found at


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


Resource Manager API uses HTTP/JSON for the transport layer.

Supported Java Versions

Java 8 or above is required for using this client.

Google's Java client libraries, Google Cloud Client Libraries and Google Cloud API Libraries, follow the Oracle Java SE support roadmap (see the Oracle Java SE Product Releases section).

For new development

In general, new feature development occurs with support for the lowest Java LTS version covered by Oracle's Premier Support (which typically lasts 5 years from initial General Availability). If the minimum required JVM for a given library is changed, it is accompanied by a semver major release.

Java 11 and (in September 2021) Java 17 are the best choices for new development.

Keeping production systems current

Google tests its client libraries with all current LTS versions covered by Oracle's Extended Support (which typically lasts 8 years from initial General Availability).

Legacy support

Google's client libraries support legacy versions of Java runtimes with long term stable libraries that don't receive feature updates on a best efforts basis as it may not be possible to backport all patches.

Google provides updates on a best efforts basis to apps that continue to use Java 7, though apps might need to upgrade to current versions of the library that supports their JVM.

Where to find specific information

The latest versions and the supported Java versions are identified on the individual GitHub repository and on google-cloud-java.


This library follows Semantic Versioning.


Contributions to this library are always welcome and highly encouraged.

See CONTRIBUTING for more information 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.


Apache 2.0 - See LICENSE for more information.

CI Status

Java Version Status
Java 8 Kokoro CI
Java 8 OSX Kokoro CI
Java 8 Windows Kokoro CI
Java 11 Kokoro CI

Java is a registered trademark of Oracle and/or its affiliates.


No description, website, or topics provided.



Code of conduct





No packages published