Class URLMapPathMatcherGetArgs
Inherited Members
Namespace: Pulumi.Gcp.Compute.Inputs
Assembly: Pulumi.Gcp.dll
Syntax
public sealed class URLMapPathMatcherGetArgs : ResourceArgs
Constructors
View SourceURLMapPathMatcherGetArgs()
Declaration
public URLMapPathMatcherGetArgs()
Properties
View SourceDefaultService
The backend service or backend bucket to use when none of the given paths match.
Declaration
public Input<string> DefaultService { get; set; }
Property Value
| Type | Description |
|---|---|
| Input<System.String> |
DefaultUrlRedirect
When none of the specified hostRules match, the request is redirected to a URL specified by defaultUrlRedirect. If defaultUrlRedirect is specified, defaultService or defaultRouteAction must not be set. Structure is documented below.
Declaration
public Input<URLMapPathMatcherDefaultUrlRedirectGetArgs> DefaultUrlRedirect { get; set; }
Property Value
| Type | Description |
|---|---|
| Input<URLMapPathMatcherDefaultUrlRedirectGetArgs> |
Description
Description of this test case.
Declaration
public Input<string> Description { get; set; }
Property Value
| Type | Description |
|---|---|
| Input<System.String> |
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<URLMapPathMatcherHeaderActionGetArgs> HeaderAction { get; set; }
Property Value
| Type | Description |
|---|---|
| Input<URLMapPathMatcherHeaderActionGetArgs> |
Name
The name of the query parameter to match. The query parameter must exist in the request, in the absence of which the request match fails.
Declaration
public Input<string> Name { get; set; }
Property Value
| Type | Description |
|---|---|
| Input<System.String> |
PathRules
The list of path rules. Use this list instead of routeRules when routing based on simple path matching is all that's required. The order by which path rules are specified does not matter. Matches are always done on the longest-path-first basis. For example: a pathRule with a path /a/b/c/* will match before /a/b/* irrespective of the order in which those paths appear in this list. Within a given pathMatcher, only one of pathRules or routeRules must be set. Structure is documented below.
Declaration
public InputList<URLMapPathMatcherPathRuleGetArgs> PathRules { get; set; }
Property Value
| Type | Description |
|---|---|
| InputList<URLMapPathMatcherPathRuleGetArgs> |
RouteRules
The list of ordered HTTP route rules. Use this list instead of pathRules when advanced route matching and routing actions are desired. The order of specifying routeRules matters: the first rule that matches will cause its specified routing action to take effect. Within a given pathMatcher, only one of pathRules or routeRules must be set. routeRules are not supported in UrlMaps intended for External load balancers. Structure is documented below.
Declaration
public InputList<URLMapPathMatcherRouteRuleGetArgs> RouteRules { get; set; }
Property Value
| Type | Description |
|---|---|
| InputList<URLMapPathMatcherRouteRuleGetArgs> |