Spoke

The time the spoke was created.

An optional description of the spoke.

Immutable. The name of the hub that this spoke is attached to.

Optional labels in key:value format. For more information about labels, see Requirements for labels.

VLAN attachments that are associated with the spoke.

Router appliance instances that are associated with the spoke.

VPN tunnels that are associated with the spoke.

Immutable. The name of the spoke. Spoke names must be unique. They use the following form: projects/{project_number}/locations/{region}/spokes/{spoke_id}

Optional. A unique request ID (optional). If you specify this ID, you can use it in cases when you need to retry your request. When you need to retry, this ID lets the server know that it can ignore the request if it has already been completed. The server guarantees that for at least 60 minutes after the first request. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check to see whether the original operation was received. If it was, the server ignores the second request. This behavior prevents clients from mistakenly creating duplicate commitments. The request ID must be a valid UUID, with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).

Required. Unique id for the spoke to create.

The current lifecycle state of this spoke.

The Google-generated UUID for the spoke. This value is unique across all spoke resources. If a spoke is deleted and another with the same name is created, the new spoke is assigned a different unique_id.

The time the spoke was last updated.