LocalCloud Cloud Resource Manager Local Emulator
Get started
local.cloud / agents
Read this page as Markdown ↗
local.cloud — Cloud Resource Manager Local Emulator .md Open tab

Cloud Resource Manager

Resource Manager organizes Google Cloud resources into projects, folders, and organizations. LocalCloud implements documented project lifecycle operations for local provisioning flows.

When to use Cloud Resource Manager

Typical uses

Use when automation needs to create, look up, or delete projects and carry their IDs through resource provisioning. Projects provide the scope for the rest of your setup.

Examples

  • Project provisioning
  • Project-scoped test environments

Explore another service

View all

Example usage

Service ID: cloudresourcemanager. Starts by default. Use an already running LocalCloud runtime for the examples below.

Export the local project and mapped endpoints in your client process, then use the client settings below. First-time setup

# Export GOOGLE_CLOUD_PROJECT and CLOUD_RESOURCE_MANAGER_EMULATOR_HOST
eval "$(localcloud env)"

REST gateway examples use the generated HTTP address in SERVICE_USAGE_EMULATOR_HOST; native SDKs can use a different protocol.

Java · REST

List local projects

List projects; Resource Manager provides the project boundaries used to organize application resources.

Call the Google Cloud REST API with the JDK HTTP client. Requires JDK 17+. Results reflect resources already created in your local project.

Discovery check · reads existing local state.

Save as Hello.java

import java.net.URI;
import java.net.http.*;
import java.time.Duration;
import java.util.Objects;

public class Hello {
  public static void main(String[] args) throws Exception {
    var project = Objects.requireNonNull(System.getenv("GOOGLE_CLOUD_PROJECT"));
    var endpoint = Objects.requireNonNull(System.getenv("SERVICE_USAGE_EMULATOR_HOST"));
    var url = URI.create(endpoint.replaceAll("/+$", "") + "/v1/projects");
    var request = HttpRequest.newBuilder(url).timeout(Duration.ofSeconds(30)).GET().build();
    var client = HttpClient.newBuilder().connectTimeout(Duration.ofSeconds(10)).build();
    var response = client.send(request, HttpResponse.BodyHandlers.ofString());
    if (response.statusCode() >= 400) {
      throw new IllegalStateException(response.statusCode() + ": " + response.body());
    }
    System.out.println(response.body());
  }
}

Run the example

java Hello.java

Verify the result

The request succeeds. An empty list or no printed rows is valid before matching resources exist. Continue with the documented workflows for a resource test.

Verify a resource workflow by creating isolated state, performing the operation, and reading the result back. Run cleanup even after a failure; delete only test-owned resources.

Connection failed? Check localcloud status --verbose, enabled services, and client exports. Stop accidental Google Cloud calls; correct local routing before retrying.

Documented workflows

  • Project CRUD through v1/v3 APIs; completed operation polling

    Create a test project through v1 or v3, read it back, and poll its completed operation. Delete owned service resources before checking project deletion.

  • Project auto-registration on supported entry points outside strict mode

    Outside strict mode, address a new project through a supported gateway entry point and verify its registration. Repeat with strict mode to test code that requires explicit project setup.

Service boundaries

  • No organization/folder lifecycle, moves, search, or full ancestry
  • No project auto-registration on direct emulator listeners
Agent testing

Use Cloud Resource Manager with an AI agent

Before the agent changes application logic, have it create local Cloud Resource Manager state, read it back with the project SDK, and note which feature the check covered. That first local call catches accidental production routing and needs no GCP account, service-account key, or billing project.

Configure this repo

Set up this repository to use LocalCloud for local GCP development. First read https://local.cloud/ai/agents.md, then inspect this repo, identify the GCP services and SDK language, configure emulator environment variables, and run the narrowest integration test against localhost. Do not use real GCP credentials or production endpoints.

Production endpoints, auth, IAM, quotas, regional behavior, and final release validation still need the target Google Cloud project.

Agent resources has more prompts and the AGENTS.md template.

Related guides

Desktop view