URLMapPathMatcherRouteRule class
Constructors
-
URLMapPathMatcherRouteRule({Input<URLMapPathMatcherRouteRuleCustomErrorResponsePolicy?>? customErrorResponsePolicy, Input<List<URLMapPathMatcherRouteRuleHttpFilterConfig>?>? httpFilterConfigs, Input<List<URLMapPathMatcherRouteRuleHttpFilterMetadata>?>? httpFilterMetadatas, Input<List<URLMapPathMatcherRouteRuleMatchRule>?>? matchRules, required Input<int> priority, Input<URLMapPathMatcherRouteRuleRouteAction?>? routeAction, Input<String?>? service, Input<URLMapPathMatcherRouteRuleUrlRedirect?>? urlRedirect})
-
Creates a new URLMapPathMatcherRouteRule.
customErrorResponsePolicy customErrorResponsePolicy specifies how the Load Balancer returns error responses when BackendService or BackendBucket responds with an error.
headerAction Specifies changes to request and response headers that need to take effect for
httpFilterConfigs (Optional, Beta)
httpFilterMetadatas (Optional, Beta)
matchRules The rules for determining a match.
priority For routeRules within a given pathMatcher, priority determines the order
routeAction In response to a matching matchRule, the load balancer performs advanced routing
service The backend service resource to which traffic is
urlRedirect When this rule is matched, the request is redirected to a URL specified by
const
-
URLMapPathMatcherRouteRule.fromMap(Map<String, dynamic> map)
-
factory
Properties
-
customErrorResponsePolicy
→ Input<URLMapPathMatcherRouteRuleCustomErrorResponsePolicy?>?
-
customErrorResponsePolicy specifies how the Load Balancer returns error responses when BackendService or BackendBucket responds with an error.
Structure is documented below.
final
-
hashCode
→ int
-
The hash code for this object.
no setterinherited
-
Specifies changes to request and response headers that need to take effect for
the selected backendService. The headerAction specified here are applied before
the matching pathMatchers[].headerAction and after pathMatchers[].routeRules[].r
outeAction.weightedBackendService.backendServiceWeightAction[].headerAction
Structure is documented below.
final
-
httpFilterConfigs
→ Input<List<URLMapPathMatcherRouteRuleHttpFilterConfig>?>?
-
(Optional, Beta)
Outbound route specific configuration for networkservices.HttpFilter resources enabled by Traffic Director.
httpFilterConfigs only applies for load balancers with loadBalancingScheme set to INTERNAL_SELF_MANAGED.
See ForwardingRule for more details.
Not supported when the URL map is bound to a target gRPC proxy that has validateForProxyless field set to true.
Structure is documented below.
final
-
httpFilterMetadatas
→ Input<List<URLMapPathMatcherRouteRuleHttpFilterMetadata>?>?
-
(Optional, Beta)
Outbound route specific metadata supplied to networkservices.HttpFilter resources enabled by Traffic Director.
httpFilterMetadata only applies for load balancers with loadBalancingScheme set to INTERNAL_SELF_MANAGED.
See ForwardingRule for more details.
Not supported when the URL map is bound to a target gRPC proxy that has validateForProxyless field set to true.
Structure is documented below.
final
-
matchRules
→ Input<List<URLMapPathMatcherRouteRuleMatchRule>?>?
-
The rules for determining a match.
Structure is documented below.
final
-
priority
→ Input<int>
-
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.
final
-
routeAction
→ Input<URLMapPathMatcherRouteRuleRouteAction?>?
-
In response to a matching matchRule, 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.
final
-
runtimeType
→ Type
-
A representation of the runtime type of the object.
no setterinherited
-
service
→ Input<String?>?
-
The backend service resource to which traffic is
directed if this rule is matched. If routeAction is additionally specified,
advanced routing actions like URL Rewrites, etc. take effect prior to sending
the request to the backend. However, if service is specified, routeAction cannot
contain any weightedBackendService s. Conversely, if routeAction specifies any
weightedBackendServices, service must not be specified. Only one of urlRedirect,
service or routeAction.weightedBackendService must be set.
final
-
urlRedirect
→ Input<URLMapPathMatcherRouteRuleUrlRedirect?>?
-
When this rule 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.
final
