pub struct URLMapResult {Show 15 fields
pub creation_timestamp: Output<String>,
pub default_custom_error_response_policy: Output<Option<UrlMapDefaultCustomErrorResponsePolicy>>,
pub default_route_action: Output<Option<UrlMapDefaultRouteAction>>,
pub default_service: Output<Option<String>>,
pub default_url_redirect: Output<Option<UrlMapDefaultUrlRedirect>>,
pub description: Output<Option<String>>,
pub fingerprint: Output<String>,
pub header_action: Output<Option<UrlMapHeaderAction>>,
pub host_rules: Output<Option<Vec<UrlMapHostRule>>>,
pub map_id: Output<i32>,
pub name: Output<String>,
pub path_matchers: Output<Option<Vec<UrlMapPathMatcher>>>,
pub project: Output<String>,
pub self_link: Output<String>,
pub tests: Output<Option<Vec<UrlMapTest>>>,
}
Fields§
§creation_timestamp: Output<String>
Creation timestamp in RFC3339 text format.
default_custom_error_response_policy: Output<Option<UrlMapDefaultCustomErrorResponsePolicy>>
defaultCustomErrorResponsePolicy specifies how the Load Balancer returns error responses when BackendService or BackendBucket responds with an error. This policy takes effect at the PathMatcher level and applies only when no policy has been defined for the error code at lower levels like RouteRule and PathRule within this PathMatcher. If an error code does not have a policy defined in defaultCustomErrorResponsePolicy, then a policy defined for the error code in UrlMap.defaultCustomErrorResponsePolicy takes effect. For example, consider a UrlMap with the following configuration: UrlMap.defaultCustomErrorResponsePolicy is configured with policies for 5xx and 4xx errors A RouteRule for /coming_soon/ is configured for the error code 404. If the request is for www.myotherdomain.com and a 404 is encountered, the policy under UrlMap.defaultCustomErrorResponsePolicy takes effect. If a 404 response is encountered for the request www.example.com/current_events/, the pathMatcher’s policy takes effect. If however, the request for www.example.com/coming_soon/ encounters a 404, the policy in RouteRule.customErrorResponsePolicy takes effect. If any of the requests in this example encounter a 500 error code, the policy at UrlMap.defaultCustomErrorResponsePolicy takes effect. When used in conjunction with pathMatcher.defaultRouteAction.retryPolicy, retries take precedence. Only once all retries are exhausted, the defaultCustomErrorResponsePolicy is applied. While attempting a retry, if load balancer is successful in reaching the service, the defaultCustomErrorResponsePolicy is ignored and the response from the service is returned to the client. defaultCustomErrorResponsePolicy is supported only for global external Application Load Balancers. Structure is documented below.
default_route_action: Output<Option<UrlMapDefaultRouteAction>>
defaultRouteAction takes effect when none of the hostRules match. The load balancer performs advanced routing actions like URL rewrites, header transformations, etc. prior to forwarding the request to the selected backend. If defaultRouteAction specifies any weightedBackendServices, defaultService must not be set. Conversely if defaultService is set, defaultRouteAction cannot contain any weightedBackendServices. Only one of defaultRouteAction or defaultUrlRedirect must be set. Structure is documented below.
default_service: Output<Option<String>>
The backend service or backend bucket to use when none of the given rules match.
default_url_redirect: Output<Option<UrlMapDefaultUrlRedirect>>
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.
description: Output<Option<String>>
An optional description of this resource. Provide this property when you create the resource.
fingerprint: Output<String>
Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking.
header_action: Output<Option<UrlMapHeaderAction>>
Specifies changes to request and response headers that need to take effect for the selected backendService. The headerAction specified here take effect after headerAction specified under pathMatcher. Structure is documented below.
host_rules: Output<Option<Vec<UrlMapHostRule>>>
The list of HostRules to use against the URL. Structure is documented below.
map_id: Output<i32>
The unique identifier for the resource.
name: Output<String>
Name of the resource. Provided by the client when the resource is created. The
name must be 1-63 characters long, and comply with RFC1035. Specifically, the
name must be 1-63 characters long and match the regular expression
a-z?
which means the first character must be a lowercase
letter, and all following characters must be a dash, lowercase letter, or digit,
except the last character, which cannot be a dash.
path_matchers: Output<Option<Vec<UrlMapPathMatcher>>>
The list of named PathMatchers to use against the URL. Structure is documented below.
project: Output<String>
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
self_link: Output<String>
The URI of the created resource.
tests: Output<Option<Vec<UrlMapTest>>>
The list of expected URL mapping tests. Request to update this UrlMap will succeed only if all of the test cases pass. You can specify a maximum of 100 tests per UrlMap. Structure is documented below.