Class RegionUrlMapPathMatcherRouteRuleArgs

Inheritance
System.Object
InputArgs
ResourceArgs
RegionUrlMapPathMatcherRouteRuleArgs
Inherited Members
System.Object.Equals(System.Object)
System.Object.Equals(System.Object, System.Object)
System.Object.GetHashCode()
System.Object.GetType()
System.Object.MemberwiseClone()
System.Object.ReferenceEquals(System.Object, System.Object)
System.Object.ToString()
Namespace: Pulumi.Gcp.Compute.Inputs
Assembly: Pulumi.Gcp.dll
Syntax
public sealed class RegionUrlMapPathMatcherRouteRuleArgs : ResourceArgs

Constructors

View Source

RegionUrlMapPathMatcherRouteRuleArgs()

Declaration
public RegionUrlMapPathMatcherRouteRuleArgs()

Properties

View Source

HeaderAction

Specifies changes to request and response headers that need to take effect for the selected backendService. headerAction specified here take effect before headerAction in the enclosing HttpRouteRule, PathMatcher and UrlMap. Structure is documented below.

Declaration
public Input<RegionUrlMapPathMatcherRouteRuleHeaderActionArgs> HeaderAction { get; set; }
Property Value
Type Description
Input<RegionUrlMapPathMatcherRouteRuleHeaderActionArgs>
View Source

MatchRules

The rules for determining a match. Structure is documented below.

Declaration
public InputList<RegionUrlMapPathMatcherRouteRuleMatchRuleArgs> MatchRules { get; set; }
Property Value
Type Description
InputList<RegionUrlMapPathMatcherRouteRuleMatchRuleArgs>
View Source

Priority

For routeRules within a given pathMatcher, priority determines the order in which load balancer will interpret routeRules. RouteRules are evaluated in order of priority, from the lowest to highest number. The priority of a rule decreases as its number increases (1, 2, 3, N+1). The first rule that matches the request is applied. You cannot configure two or more routeRules with the same priority. Priority for each rule must be set to a number between 0 and 2147483647 inclusive. Priority numbers can have gaps, which enable you to add or remove rules in the future without affecting the rest of the rules. For example, 1, 2, 3, 4, 5, 9, 12, 16 is a valid series of priority numbers to which you could add rules numbered from 6 to 8, 10 to 11, and 13 to 15 in the future without any impact on existing rules.

Declaration
public Input<int> Priority { get; set; }
Property Value
Type Description
Input<System.Int32>
View Source

RouteAction

In response to a matching path, the load balancer performs advanced routing actions like URL rewrites, header transformations, etc. prior to forwarding the request to the selected backend. If routeAction specifies any weightedBackendServices, service must not be set. Conversely if service is set, routeAction cannot contain any weightedBackendServices. Only one of routeAction or urlRedirect must be set. Structure is documented below.

Declaration
public Input<RegionUrlMapPathMatcherRouteRuleRouteActionArgs> RouteAction { get; set; }
Property Value
Type Description
Input<RegionUrlMapPathMatcherRouteRuleRouteActionArgs>
View Source

Service

A reference to expected RegionBackendService resource the given URL should be mapped to.

Declaration
public Input<string> Service { get; set; }
Property Value
Type Description
Input<System.String>
View Source

UrlRedirect

When a path pattern is matched, the request is redirected to a URL specified by urlRedirect. If urlRedirect is specified, service or routeAction must not be set. Structure is documented below.

Declaration
public Input<RegionUrlMapPathMatcherRouteRuleUrlRedirectArgs> UrlRedirect { get; set; }
Property Value
Type Description
Input<RegionUrlMapPathMatcherRouteRuleUrlRedirectArgs>