Application Load Balancer API, REST: LoadBalancer.update

Required. ID of the application load balancer to update.

To get the application load balancer ID, make a list request.

Field mask that specifies which attributes of the application load balancer should be updated.

A comma-separated names off ALL fields to be updated. Only the specified fields will be changed. The others will be left untouched. If the field is specified in updateMask and no value for that field was sent in the request, the field's value will be reset to the default. The default value for most fields is null or 0.

If updateMask is not sent in the request, all fields' values will be updated. Fields specified in the request will be updated to provided values. The rest of the fields will be reset to the default.

New name for the application load balancer. The name must be unique within the folder.

Value must match the regular expression ([a-z]([-a-z0-9]{0,61}[a-z0-9])?)?.

New description of the application load balancer.

The maximum string length in characters is 256.

New application load balancer labels as key:value pairs. For details about the concept, see documentation.

Existing set of labels is completely replaced by the provided set, so if you just want to add or remove a label:

1. Get the current set of labels with a get request.
2. Add or remove a label in this set.
3. Send the new set in this field.

No more than 64 per resource. The string length in characters for each key must be 1-63. Each key must match the regular expression [a-z][-_./\@0-9a-z]*. The maximum string length in characters for each value is 63. Each value must match the regular expression [-_./\@0-9a-z]*.

New listeners for the application load balancer.

For details about the concept, see documentation.

Existing list of listeners is completely replaced by the specified list, so if you just want to add, update, or remove a listener, make a addListener request, a updateListener request, or a removeListener request.

Required. Name of the listener. The name is unique within the application load balancer.

Value must match the regular expression [a-z]([-a-z0-9]{0,61}[a-z0-9])?.

Required. Endpoints of the listener.

Endpoints are defined by their IP addresses and ports.

Must contain at least one element.

Required. Endpoint public (external) and internal addresses.

Must contain at least one element.

IPv4 address.

IPv4 address.

ID of the subnet that the address belongs to.

IPv6 address.

Required. Endpoint ports.

Must contain at least one element. Acceptable values are 1 to 65535, inclusive.

Settings for handling HTTP requests.

Only one of handler and redirects can be specified.

An HTTP handler resource.

ID of the HTTP router processing requests. For details about the concept, see documentation.

To get the list of all available HTTP routers, make a list request.

When unset, will preserve the incoming x-request-id header, otherwise would rewrite it with a new value.

Maximum number of concurrent HTTP/2 streams in a connection.

Enables support for incoming HTTP/1.0 and HTTP/1.1 requests and disables it for HTTP/2 requests.

Redirects settings.

Only one of redirects and handler can be specified.

A listener redirects resource.

Redirects all unencrypted HTTP requests to the same URI with scheme changed to https.

The setting has the same effect as a single, catch-all HttpRoute with replaceScheme set to https.

Required. Settings for handling requests by default, with Server Name Indication (SNI) not matching any of the sniHandlers.

A TLS-encrypted (HTTP or TCP stream) handler resource.

Required. ID's of the TLS server certificates from Certificate Manager.

RSA and ECDSA certificates are supported, and only the first certificate of each type is used.

Must contain at least one element.

ID of the HTTP router processing requests. For details about the concept, see documentation.

To get the list of all available HTTP routers, make a list request.

When unset, will preserve the incoming x-request-id header, otherwise would rewrite it with a new value.

Maximum number of concurrent HTTP/2 streams in a connection.

Enables support for incoming HTTP/1.0 and HTTP/1.1 requests and disables it for HTTP/2 requests.

Required. ID of the backend group processing requests. For details about the concept, see documentation.

The backend group type, specified via [BackendGroup.backend], must be stream.

To get the list of all available backend groups, make a list request.

Settings for handling requests with Server Name Indication (SNI) matching one of serverNames values.

Required. Name of the SNI handler.

Required. Server names that are matched by the SNI handler.

Must contain at least one element.

Required. Settings for handling requests with Server Name Indication (SNI) matching one of serverNames values.

A TLS-encrypted (HTTP or TCP stream) handler resource.

Required. ID's of the TLS server certificates from Certificate Manager.

RSA and ECDSA certificates are supported, and only the first certificate of each type is used.

Must contain at least one element.

ID of the HTTP router processing requests. For details about the concept, see documentation.

To get the list of all available HTTP routers, make a list request.

When unset, will preserve the incoming x-request-id header, otherwise would rewrite it with a new value.

Maximum number of concurrent HTTP/2 streams in a connection.

Enables support for incoming HTTP/1.0 and HTTP/1.1 requests and disables it for HTTP/2 requests.

Required. ID of the backend group processing requests. For details about the concept, see documentation.

The backend group type, specified via [BackendGroup.backend], must be stream.

To get the list of all available backend groups, make a list request.

Required. Settings for handling stream (TCP) requests.

A stream (TCP) handler resource.

Required. ID of the backend group processing requests. For details about the concept, see documentation.

The backend group type, specified via [BackendGroup.backend], must be stream.

To get the list of all available backend groups, make a list request.

New locality settings of the application load balancer.

For details about the concept, see documentation.

Existing locality settings are completely replaced by the specified settings, so if you just want to add or remove an allocation policy:

1. Get the current settings with a get request.
2. Add or remove a policy in this set.
3. Send the new set in this field.

A locality settings (allocation policy) resource.

Required. Availability zones and subnets that the application load balancer resides.

The minimum number of elements is 1.

Required. ID of the availability zone where the application load balancer resides.

Each availability zone can only be specified once.

ID of the subnet that the application load balancer belongs to.

Disables the load balancer node in the specified availability zone.

Backends in the availability zone are not directly affected by this setting. They still may receive traffic from the load balancer nodes in other availability zones, subject to localityAwareRoutingPercent and strictLocality settings.

ID's of new security groups attributed to the application load balancer.

For details about the concept, see documentation.

Existing list of security groups is completely replaced by the specified list, so if you just want to add or remove an allocation policy:

1. Get the current set of security groups with a get request.
2. Add or remove a group in this set.
3. Send the new set in this field.

New scaling settings of the application load balancer.

The scaling settings relate to a special internal instance group which facilitates the balancer's work. Instances in this group are called resource units. The group is scaled automatically based on incoming load and within limitations specified in these settings.

For details about the concept, see documentation.

A resource for scaling settings of an application load balancer.

Lower limit for the number of resource units in each availability zone.

If not specified previously (using other instruments such as management console), the default value is 2. To revert to it, specify it explicitly.

The minimum value is 2.

Acceptable values are 0 to 1000, inclusive.

Upper limit for the total number of resource units across all availability zones.

If a positive value is specified, it must be at least minZoneSize multiplied by the size of locations.

If the value is 0, there is no upper limit.

Acceptable values are 0 to 1000, inclusive.

Cloud logging settings of the application load balancer.

Cloud Logging log group ID to store access logs. If not set then logs will be stored in default log group for the folder where load balancer located.

ordered list of rules, first matching rule applies

HTTP codes that should be discarded.

Acceptable values are 100 to 599, inclusive.

Groups of HTTP codes like 4xx that should be discarded.

GRPC codes that should be discarded

• OK: Not an error; returned on success

  HTTP Mapping: 200 OK

• CANCELLED: The operation was cancelled, typically by the caller.

  HTTP Mapping: 499 Client Closed Request

• UNKNOWN: Unknown error. For example, this error may be returned when a Status value received from another address space belongs to an error space that is not known in this address space. Also errors raised by APIs that do not return enough error information may be converted to this error.

  HTTP Mapping: 500 Internal Server Error

• INVALID_ARGUMENT: The client specified an invalid argument. Note that this differs from FAILED_PRECONDITION. INVALID_ARGUMENT indicates arguments that are problematic regardless of the state of the system (e.g., a malformed file name).

  HTTP Mapping: 400 Bad Request

• DEADLINE_EXCEEDED: The deadline expired before the operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully. For example, a successful response from a server could have been delayed long enough for the deadline to expire.

  HTTP Mapping: 504 Gateway Timeout

• NOT_FOUND: Some requested entity (e.g., file or directory) was not found.

  Note to server developers: if a request is denied for an entire class of users, such as gradual feature rollout or undocumented whitelist, NOT_FOUND may be used. If a request is denied for some users within a class of users, such as user-based access control, PERMISSION_DENIED must be used.

  HTTP Mapping: 404 Not Found

• ALREADY_EXISTS: The entity that a client attempted to create (e.g., file or directory) already exists.

  HTTP Mapping: 409 Conflict

• PERMISSION_DENIED: The caller does not have permission to execute the specified operation. PERMISSION_DENIED must not be used for rejections caused by exhausting some resource (use RESOURCE_EXHAUSTED instead for those errors). PERMISSION_DENIED must not be used if the caller can not be identified (use UNAUTHENTICATED instead for those errors). This error code does not imply the request is valid or the requested entity exists or satisfies other pre-conditions.

  HTTP Mapping: 403 Forbidden

• UNAUTHENTICATED: The request does not have valid authentication credentials for the operation.

  HTTP Mapping: 401 Unauthorized

• RESOURCE_EXHAUSTED: Some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space.

  HTTP Mapping: 429 Too Many Requests

• FAILED_PRECONDITION: The operation was rejected because the system is not in a state required for the operation's execution. For example, the directory to be deleted is non-empty, an rmdir operation is applied to a non-directory, etc.

  Service implementors can use the following guidelines to decide between FAILED_PRECONDITION, ABORTED, and UNAVAILABLE: (a) Use UNAVAILABLE if the client can retry just the failing call. (b) Use ABORTED if the client should retry at a higher level (e.g., when a client-specified test-and-set fails, indicating the client should restart a read-modify-write sequence). (c) Use FAILED_PRECONDITION if the client should not retry until the system state has been explicitly fixed. E.g., if an "rmdir" fails because the directory is non-empty, FAILED_PRECONDITION should be returned since the client should not retry unless the files are deleted from the directory.

  HTTP Mapping: 400 Bad Request

• ABORTED: The operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort.

  See the guidelines above for deciding between FAILED_PRECONDITION, ABORTED, and UNAVAILABLE.

  HTTP Mapping: 409 Conflict

• OUT_OF_RANGE: The operation was attempted past the valid range. E.g., seeking or reading past end-of-file.

  Unlike INVALID_ARGUMENT, this error indicates a problem that may be fixed if the system state changes. For example, a 32-bit file system will generate INVALID_ARGUMENT if asked to read at an offset that is not in the range [0,2^32-1], but it will generate OUT_OF_RANGE if asked to read from an offset past the current file size.

  There is a fair bit of overlap between FAILED_PRECONDITION and OUT_OF_RANGE. We recommend using OUT_OF_RANGE (the more specific error) when it applies so that callers who are iterating through a space can easily look for an OUT_OF_RANGE error to detect when they are done.

  HTTP Mapping: 400 Bad Request

• UNIMPLEMENTED: The operation is not implemented or is not supported/enabled in this service.

  HTTP Mapping: 501 Not Implemented

• INTERNAL: Internal errors. This means that some invariants expected by the underlying system have been broken. This error code is reserved for serious errors.

  HTTP Mapping: 500 Internal Server Error

• UNAVAILABLE: The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff.

  See the guidelines above for deciding between FAILED_PRECONDITION, ABORTED, and UNAVAILABLE.

  HTTP Mapping: 503 Service Unavailable

• DATA_LOSS: Unrecoverable data loss or corruption.

  HTTP Mapping: 500 Internal Server Error

Percent of logs to be discarded: 0 - keep all, 100 or unset - discard all

Acceptable values are 0 to 100, inclusive.

Do not send logs to Cloud Logging log group.

ID of the operation.

Description of the operation. 0-256 characters long.

Creation timestamp.

String in RFC3339 text format. The range of possible values is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z, i.e. from 0 to 9 digits for fractions of a second.

To work with values in this field, use the APIs described in the Protocol Buffers reference. In some languages, built-in datetime utilities do not support nanosecond precision (9 digits).

ID of the user or service account who initiated the operation.

The time when the Operation resource was last modified.

String in RFC3339 text format. The range of possible values is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z, i.e. from 0 to 9 digits for fractions of a second.

To work with values in this field, use the APIs described in the Protocol Buffers reference. In some languages, built-in datetime utilities do not support nanosecond precision (9 digits).

If the value is false, it means the operation is still in progress. If true, the operation is completed, and either error or response is available.

Service-specific metadata associated with the operation. It typically contains the ID of the target resource that the operation is performed on. Any method that returns a long-running operation should document the metadata type, if any.

Error code. An enum value of google.rpc.Code.

An error message.

A list of messages that carry the error details.

The normal response of the operation in case of success. If the original method returns no data on success, such as Delete, the response is google.protobuf.Empty. If the original method is the standard Create/Update, the response should be the target resource of the operation. Any method that returns a long-running operation should document the response type, if any.