Locations

Every regional GCP API also serves the google.cloud.location.Locations mixin (locations.proto). floci-gcp answers it from one bundled catalog of real GCP locations: 43 regions and their 130 zones, taken from Regions and zones. The same catalog drives Compute Engine regions and zones, and the optional strict location check described below.

Endpoints

Protocol	Method	Path / RPC
REST	GET	/v1/projects/{project}/locations
REST	GET	/v1/projects/{project}/locations/{location}
REST	GET	/v2/projects/{project}/locations
REST	GET	/v2/projects/{project}/locations/{location}
gRPC	ListLocations, GetLocation	google.cloud.location.Locations

The v1 paths are the ones Cloud KMS, Cloud Scheduler, Eventarc, Managed Kafka, Secret Manager and Cloud Run v1 use. The v2 paths are the ones Cloud Tasks and Cloud Functions v2 use. Cloud Functions only defines list, but serving get on v2 as well does no harm.

List returns one entry per catalog region, plus KMS's global, us, europe and asia unless the request names a different API (see below). It always includes the locations array, even when it is empty: the Terraform google_cloud_run_locations data source needs that array to be present.

{
  "locations": [
    {
      "name": "projects/my-project/locations/us-central1",
      "locationId": "us-central1",
      "displayName": "Council Bluffs",
      "labels": {"cloud.googleapis.com/region": "us-central1"}
    }
  ]
}

• displayName is the city from the "Location" column of the regions-and-zones table.
• pageSize and pageToken page through the list, and nextPageToken is set while more pages remain. filter is ignored.
• Get returns NOT_FOUND for an id that is not in the list.

Which locations each caller sees

On a single port, the path does not say which API is being called. For REST, floci-gcp reads the first label of the Host header. A client that reaches floci-gcp under the real hostname (for example through the embedded DNS and TLS on port 443) gets the exact list for that API:

Host	Locations	Metadata
cloudkms.*	catalog regions, global, us, europe, asia	google.cloud.kms.v1.LocationMetadata with hsmAvailable and ekmAvailable set to false, because the emulator keeps software keys only
cloudfunctions.*	catalog regions	google.cloud.functions.v2.LocationMetadata with environments: ["GEN_2"]
run.*, cloudtasks.*, cloudscheduler.*, eventarc.*, managedkafka.*, secretmanager.*	catalog regions	none

Every other caller gets the catalog regions plus KMS's four extra locations, with no metadata. That covers gRPC (the gRPC bridge does not expose the call authority) and any REST host that names no API, such as localhost or a Docker service name, which is what endpoint overrides usually send. KMS clients need those four locations, so the others see them too: for example, gcloud run regions list through an endpoint override lists global, us, europe and asia, which Cloud Run does not accept in strict mode.

Strict location validation

By default floci-gcp accepts any location string, as it always has. Set FLOCI_GCP_LOCATIONS_STRICT=true (floci-gcp.locations.strict) to reject unknown locations with INVALID_ARGUMENT (Invalid location: {location}). Google does not document the exact error text, so this wording is floci-gcp's own.

API	Checked on	Accepted locations
Cloud Run v2	service, job, worker pool, instance create and list	catalog regions
Cloud Functions v2	function create, function list	catalog regions
Cloud KMS	key ring create, key ring list	catalog regions, global, us, europe, asia
Cloud Tasks	queue create, queue list	catalog regions
Cloud Scheduler	job create, job list	catalog regions
Eventarc	trigger create, trigger list	catalog regions
Managed Kafka	cluster create, cluster list	catalog regions
GKE	cluster create, cluster list	catalog regions and zones

The - list wildcard is never checked. Strict mode does not accept KMS dual-regional locations such as nam-eur-asia1 yet, because the bundled reference does not list them. Compute Engine does not use this setting. It always answers 404 for a region or zone that is not configured.

Configuration

Variable	Default	Description
FLOCI_GCP_LOCATIONS_STRICT	false	Reject unknown locations on regional create and list calls
FLOCI_GCP_SERVICES_COMPUTE_REGIONS	(unset)	Optional Compute Engine region allow-list. Unset means the full catalog

The Locations endpoints are always on. They are not tied to any service's enabled flag.