Skip to content

Commit

Permalink
Add support for INTERNAL_SELF_MANAGED backend service
Browse files Browse the repository at this point in the history
Signed-off-by: Modular Magician <[email protected]>
  • Loading branch information
slevenick authored and modular-magician committed May 31, 2019
1 parent 843a43c commit 0269f57
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/resources/google_compute_backend_service.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ Properties that can be accessed from the `google_compute_backend_service` resour

* `enable_cdn`: If true, enable Cloud CDN for this BackendService.

* `health_checks`: The list of URLs to the HttpHealthCheck or HttpsHealthCheck resource for health checking this BackendService. Currently at most one health check can be specified, and a health check is required.
* `health_checks`: The list of URLs to the HttpHealthCheck or HttpsHealthCheck resource for health checking this BackendService. Currently at most one health check can be specified, and a health check is required. For internal load balancing, a URL to a HealthCheck resource must be specified instead.

* `id`: The unique identifier for the resource.

Expand All @@ -79,7 +79,7 @@ Properties that can be accessed from the `google_compute_backend_service` resour

* `oauth2_client_secret_sha256`: OAuth2 Client Secret SHA-256 for IAP

* `load_balancing_scheme`: Indicates whether the backend service will be used with internal or external load balancing. A backend service created for one type of load balancing cannot be used with the other. Must be `EXTERNAL` for a global backend service. Defaults to `EXTERNAL`.
* `load_balancing_scheme`: Indicates whether the backend service will be used with internal or external load balancing. A backend service created for one type of load balancing cannot be used with the other. Must be `EXTERNAL` or `INTERNAL_SELF_MANAGED` for a global backend service. Defaults to `EXTERNAL`.

* `name`: Name of the resource. Provided by the client when the resource is created. 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.

Expand Down

0 comments on commit 0269f57

Please sign in to comment.