HttpRouteArgs class

The set of arguments for HttpRoute. The set of arguments for HttpRoute.

Constructors

HttpRouteArgs({Input<String>? description, Input<List<String>>? gateways, required Input<List<String>> hostnames, required Input<String> httpRouteId, Input<Map<String, String>>? labels, Input<String>? location, Input<List<String>>? meshes, Input<String>? name, Input<String>? project, required Input<List<HttpRouteRouteRule>> rules})

Creates a new HttpRouteArgs. description Optional. A free-text description of the resource. Max length 1024 characters. gateways Optional. Gateways defines a list of gateways this HttpRoute is attached to, as one of the routing rules to route the requests served by the gateway. Each gateway reference should match the pattern: projects/*/locations/global/gateways/ hostnames Hostnames define a set of hosts that should match against the HTTP host header to select a HttpRoute to process the request. Hostname is the fully qualified domain name of a network host, as defined by RFC 1123 with the exception that: - IPs are not allowed. - A hostname may be prefixed with a wildcard label (*.). The wildcard label must appear by itself as the first label. Hostname can be "precise" which is a domain name without the terminating dot of a network host (e.g. foo.example.com) or "wildcard", which is a domain name prefixed with a single wildcard label (e.g. *.example.com). Note that as per RFC1035 and RFC1123, a label must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character. No other punctuation is allowed. The routes associated with a Mesh or Gateways must have unique hostnames. If you attempt to attach multiple routes with conflicting hostnames, the configuration will be rejected. For example, while it is acceptable for routes for the hostnames *.foo.bar.com and *.bar.com to be associated with the same Mesh (or Gateways under the same scope), it is not possible to associate two routes both with *.bar.com or both with bar.com. httpRouteId Required. Short name of the HttpRoute resource to be created. labels Optional. Set of label tags associated with the HttpRoute resource. location Optional. meshes Optional. Meshes defines a list of meshes this HttpRoute is attached to, as one of the routing rules to route the requests served by the mesh. Each mesh reference should match the pattern: projects/*/locations/global/meshes/ The attached Mesh should be of a type SIDECAR name Name of the HttpRoute resource. It matches pattern projects/*/locations/global/httpRoutes/http_route_name>. project Optional. rules Rules that define how traffic is routed and handled. Rules will be matched sequentially based on the RouteMatch specified for the rule.

const

HttpRouteArgs.fromMap(Map<String, dynamic> map)

factory

Properties

description → Input<String>?

Optional. A free-text description of the resource. Max length 1024 characters.

final

gateways → Input<List<String>>?

Optional. Gateways defines a list of gateways this HttpRoute is attached to, as one of the routing rules to route the requests served by the gateway. Each gateway reference should match the pattern: projects/*/locations/global/gateways/

final

hashCode → int

The hash code for this object.

no setter, inherited

hostnames → Input<List<String>>

Hostnames define a set of hosts that should match against the HTTP host header to select a HttpRoute to process the request. Hostname is the fully qualified domain name of a network host, as defined by RFC 1123 with the exception that: - IPs are not allowed. - A hostname may be prefixed with a wildcard label (*.). The wildcard label must appear by itself as the first label. Hostname can be "precise" which is a domain name without the terminating dot of a network host (e.g. foo.example.com) or "wildcard", which is a domain name prefixed with a single wildcard label (e.g. *.example.com). Note that as per RFC1035 and RFC1123, a label must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character. No other punctuation is allowed. The routes associated with a Mesh or Gateways must have unique hostnames. If you attempt to attach multiple routes with conflicting hostnames, the configuration will be rejected. For example, while it is acceptable for routes for the hostnames *.foo.bar.com and *.bar.com to be associated with the same Mesh (or Gateways under the same scope), it is not possible to associate two routes both with *.bar.com or both with bar.com.

final

httpRouteId → Input<String>

Required. Short name of the HttpRoute resource to be created.

final

labels → Input<Map<String, String>>?

Optional. Set of label tags associated with the HttpRoute resource.

final

location → Input<String>?

final

meshes → Input<List<String>>?

Optional. Meshes defines a list of meshes this HttpRoute is attached to, as one of the routing rules to route the requests served by the mesh. Each mesh reference should match the pattern: projects/*/locations/global/meshes/ The attached Mesh should be of a type SIDECAR

final

name → Input<String>?

Name of the HttpRoute resource. It matches pattern projects/*/locations/global/httpRoutes/http_route_name>.

final

project → Input<String>?

final

rules → Input<List<HttpRouteRouteRule>>

Rules that define how traffic is routed and handled. Rules will be matched sequentially based on the RouteMatch specified for the rule.

final

runtimeType → Type

A representation of the runtime type of the object.

no setter, inherited

Methods

noSuchMethod(Invocation invocation) → dynamic

Invoked when a nonexistent method or property is accessed.

inherited

toMap() → Map<String, dynamic>

toString() → String

A string representation of this object.

inherited

Operators

operator ==(Object other) → bool

The equality operator.

inherited