Skip to content
This repository has been archived by the owner on Nov 14, 2024. It is now read-only.

Add SHARED_LOADBALANCER_VIP purpose to regional addresses. #482

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/resources/google_compute_address.md
Original file line number Diff line number Diff line change
Expand Up @@ -68,9 +68,10 @@ Properties that can be accessed from the `google_compute_address` resource:

* `name`: Name of the resource. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression `[a-z]([-a-z0-9]*[a-z0-9])?` which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.

* `purpose`: The purpose of this resource, which can be one of the following values: * GCE_ENDPOINT for addresses that are used by VM instances, alias IP ranges, internal load balancers, and similar resources. * SHARED_LOADBALANCER_VIP for an address that can be used by multiple internal load balancers. This should only be set when using an Internal address.
* `purpose`: The purpose of this resource, which can be one of the following values: * GCE_ENDPOINT for addresses that are used by VM instances, alias IP ranges, internal load balancers, and similar resources. * SHARED_LOADBALANCER_VIP for an address that can be used by multiple internal load balancers. * VPC_PEERING for addresses that are reserved for VPC peer networks. This should only be set when using an Internal address.
Possible values:
* GCE_ENDPOINT
* VPC_PEERING
* SHARED_LOADBALANCER_VIP

* `network_tier`: The networking tier used for configuring this address. If this field is not specified, it is assumed to be PREMIUM.
Expand Down