Get Location
const url = 'https://example.com/topology/v1/engines/example/locations/example';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/topology/v1/engines/example/locations/exampleResolves a location reference to its kind and usability status in one read. Use - to resolve a
reference whose provider the caller does not know.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The cloud provider, or - to resolve regardless of provider
The unique identifier of the location to resolve
Responses
Section titled “ Responses ”OK
Location
The lean, engine-agnostic catalogue projection of a place a resource can be deployed. It answers “what kind of place is this, and is it usable?” in one read. Kind-specific detail (a region’s backing cluster, a zone’s parent region, a multi-region’s members) is served by the typed GetRegion / GetZone / GetMultiRegion resources, not here.
object
The stable unique identifier of the location (the weak-reference target carried by other resources)
The handle of the location, e.g. “global” or “us-east-1”
The kind of location (global, multi-region, region, or zone)
A human-readable label for the location
The usability status of the location
The cloud provider that backs the location
The timestamp when the location was created
The timestamp when the location was last updated
Example
{ "kind": "LOCATION_KIND_UNSPECIFIED", "status": "LOCATION_STATUS_UNSPECIFIED", "engine": "ENGINE_UNSPECIFIED"}default
Section titled “default ”Default error response
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.
Example generated
{ "code": 1, "message": "example", "details": [ { "@type": "example" } ]}