Compute V1 Client - Class NetworkEndpointGroupCloudFunction (1.6.1)

Reference documentation and code samples for the Compute V1 Client class NetworkEndpointGroupCloudFunction.

Configuration for a Cloud Function network endpoint group (NEG). The function must be provided explicitly or in the URL mask. Note: Cloud Function must be in the same project and located in the same region as the Serverless NEG.

Generated from protobuf message google.cloud.compute.v1.NetworkEndpointGroupCloudFunction

Methods

__construct

Constructor.

Parameters
NameDescription
data array

Optional. Data for populating the Message object.

↳ function string

A user-defined name of the Cloud Function. The function name is case-sensitive and must be 1-63 characters long. Example value: "func1".

↳ url_mask string

A template to parse function field from a request URL. URL mask allows for routing to multiple Cloud Functions without having to create multiple Network Endpoint Groups and backend services. For example, request URLs " mydomain.com/function1" and "mydomain.com/function2" can be backed by the same Serverless NEG with URL mask "/

getFunction

A user-defined name of the Cloud Function. The function name is case-sensitive and must be 1-63 characters long. Example value: "func1".

Returns
TypeDescription
string

hasFunction

clearFunction

setFunction

A user-defined name of the Cloud Function. The function name is case-sensitive and must be 1-63 characters long. Example value: "func1".

Parameter
NameDescription
var string
Returns
TypeDescription
$this

getUrlMask

A template to parse function field from a request URL. URL mask allows for routing to multiple Cloud Functions without having to create multiple Network Endpoint Groups and backend services. For example, request URLs " mydomain.com/function1" and "mydomain.com/function2" can be backed by the same Serverless NEG with URL mask "/

Returns
TypeDescription
string

hasUrlMask

clearUrlMask

setUrlMask

A template to parse function field from a request URL. URL mask allows for routing to multiple Cloud Functions without having to create multiple Network Endpoint Groups and backend services. For example, request URLs " mydomain.com/function1" and "mydomain.com/function2" can be backed by the same Serverless NEG with URL mask "/

Parameter
NameDescription
var string
Returns
TypeDescription
$this