Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make RegionBackendService health checks optional #4053

Merged
merged 1 commit into from
Oct 5, 2020
Merged

Make RegionBackendService health checks optional #4053

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 6 additions & 3 deletions products/compute/api.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1115,7 +1115,8 @@ objects:
for health checking this BackendService. Currently at most one health
check can be specified.

A health check must be specified unless the backend service uses an internet NEG as a backend.
A health check must be specified unless the backend service uses an internet
or serverless NEG as a backend.

For internal load balancing, a URL to a HealthCheck resource must be specified instead.
- !ruby/object:Api::Type::Integer
Expand Down Expand Up @@ -1960,13 +1961,15 @@ objects:
- !ruby/object:Api::Type::Array
name: 'healthChecks'
item_type: Api::Type::String
required: true
min_size: 1
max_size: 1
description: |
The set of URLs to HealthCheck resources for health checking
this RegionBackendService. Currently at most one health
check can be specified, and a health check is required.
check can be specified.

A health check must be specified unless the backend service uses an internet
or serverless NEG as a backend.
- !ruby/object:Api::Type::Integer
name: 'id'
description: 'The unique identifier for the resource.'
Expand Down