|
43 | 43 | "refs": { } |
44 | 44 | }, |
45 | 45 | "AwsCloudMapInstanceAttribute": { |
46 | | - "base": "<p>An object representing the AWS Cloud Map attribute information for your virtual\n node.</p>", |
| 46 | + "base": "<p>An object representing the AWS Cloud Map attribute information for your virtual node.</p>", |
47 | 47 | "refs": { |
48 | | - "AwsCloudMapInstanceAttribute$key": "<p>The name of an AWS Cloud Map service instance attribute key. Any AWS Cloud Map service\n instance that contains the specified key and value is returned.</p>", |
| 48 | + "AwsCloudMapInstanceAttribute$key": "<p>The name of an AWS Cloud Map service instance attribute key. Any AWS Cloud Map service instance\n that contains the specified key and value is returned.</p>", |
49 | 49 | "AwsCloudMapInstanceAttribute$value": "<p>The value of an AWS Cloud Map service instance attribute key. Any AWS Cloud Map service\n instance that contains the specified key and value is returned.</p>" |
50 | 50 | } |
51 | 51 | }, |
|
344 | 344 | "refs": { } |
345 | 345 | }, |
346 | 346 | "HeaderMatchMethod": { |
347 | | - "base": "<p>An object representing the method and value to match the header value sent with a\n request. Specify one match method.</p>", |
| 347 | + "base": "<p>An object representing the method and value to match the header value sent with a request. Specify one match method.</p>", |
348 | 348 | "refs": { |
349 | 349 | "HeaderMatchMethod$exact": "<p>The header value sent by the client must match the specified value exactly.</p>", |
350 | 350 | "HeaderMatchMethod$prefix": "<p>The header value sent by the client must begin with the specified characters.</p>", |
351 | | - "HeaderMatchMethod$range": "<p>The object that specifies the range of numbers within which the header value sent by the client\n must be included.</p>", |
| 351 | + "HeaderMatchMethod$range": "<p>The object that specifies the range of numbers that the header value sent by the client must be included in.</p>", |
352 | 352 | "HeaderMatchMethod$regex": "<p>The header value sent by the client must include the specified characters.</p>", |
353 | 353 | "HeaderMatchMethod$suffix": "<p>The header value sent by the client must end with the specified characters.</p>" |
354 | 354 | } |
|
405 | 405 | "HttpRouteHeader": { |
406 | 406 | "base": "<p>An object representing the HTTP header in the request.</p>", |
407 | 407 | "refs": { |
408 | | - "HttpRouteHeader$invert": "<p>Specify <code>True</code> to match the opposite of the <code>HeaderMatchMethod</code>\n method and value. The default value is <code>False</code>.</p>", |
| 408 | + "HttpRouteHeader$invert": "<p>Specify <code>True</code> to match the opposite of the <code>HeaderMatchMethod</code> method and value. The default value is <code>False</code>.</p>", |
409 | 409 | "HttpRouteHeader$match": "<p>The <code>HeaderMatchMethod</code> object.</p>", |
410 | 410 | "HttpRouteHeader$name": "<p>A name for the HTTP header in the client request that will be matched on.</p>" |
411 | 411 | } |
|
422 | 422 | "HttpRouteMatch$headers": "<p>The client request headers to match on.</p>", |
423 | 423 | "HttpRouteMatch$method": "<p>The client request header method to match on.</p>", |
424 | 424 | "HttpRouteMatch$prefix": "<p>Specifies the path to match requests with. This parameter must always start with\n <code>/</code>, which by itself matches all requests to the virtual service name. You\n can also match for path-based routing of requests. For example, if your virtual service\n name is <code>my-service.local</code> and you want the route to match requests to\n <code>my-service.local/metrics</code>, your prefix should be\n <code>/metrics</code>.</p>", |
425 | | - "HttpRouteMatch$scheme": "<p>The client request scheme to match on.</p>" |
| 425 | + "HttpRouteMatch$scheme": "<p>The client request header scheme to match on.</p>" |
426 | 426 | } |
427 | 427 | }, |
428 | 428 | "HttpScheme": { |
|
571 | 571 | "refs": { } |
572 | 572 | }, |
573 | 573 | "MatchRange": { |
574 | | - "base": "<p>The range of values to match on. The first character of the range is included in the\n range, though the last character is not. For example, if the range specified were 1-100,\n only values 1-99 would be matched.</p>", |
| 574 | + "base": "<p>The range of values to match on. The first character of the range is included in the range, though the last character is not. For example, if the range specified were 1-100, only values 1-99 would be matched.</p>", |
575 | 575 | "refs": { |
576 | | - "MatchRange$end": "<p>End of the range value.</p>", |
577 | | - "MatchRange$start": "<p>Start of the range value.</p>" |
| 576 | + "MatchRange$end": "<p>The end of the range.</p>", |
| 577 | + "MatchRange$start": "<p>The start of the range.</p>" |
578 | 578 | } |
579 | 579 | }, |
580 | 580 | "MeshData": { |
|
690 | 690 | "base": "<p>An object representing the specification of a route.</p>", |
691 | 691 | "refs": { |
692 | 692 | "RouteSpec$httpRoute": "<p>The HTTP routing information for the route.</p>", |
693 | | - "RouteSpec$priority": "<p>The priority for the route. Routes are matched based on the specified value, where 0 is\n the highest priority.</p>", |
| 693 | + "RouteSpec$priority": "<p>The priority for the route. Routes are matched based on the specified value, where 0 is the highest priority.</p>", |
694 | 694 | "RouteSpec$tcpRoute": "<p>The TCP routing information for the route.</p>" |
695 | 695 | } |
696 | 696 | }, |
|
0 commit comments