Skip to content

Latest commit

 

History

History
36 lines (24 loc) · 1.72 KB

README.md

File metadata and controls

36 lines (24 loc) · 1.72 KB

ESPv2 Configurations Testdata

Similar to ESPv2 Configurations, but primarily for:

  • Full Config Manager bootstrap tests
  • Explaining config translation to developers

Path Matcher

Configuration for the Path Matcher filter.

Specifically, this tests constant address path translation, where the request has path parameters (aka variable bindings) in snake_case vs jsonCase.

Operation Name (Selector):

  • In the OpenAPI specification, the path and HTTP method serve as a unique ID. See the OpenAPI docs for more information
  • In the generated service configuration, the api.methods.name serves as a unique ID (such as GetShelf). All other fields in the proto contain references to the operation name via the selector field.

Variable Bindings:

  • In the OpenAPI specification, Path Templates can be used.
  • The generated service configuration preserves these fields, as seen in http.rules.get.
  • Under certain scenarios, the path matcher filter must parse these variable bindings. See Understanding path translation for more information.

Sidecar Backend

Configuration for ESPv2 in sidecar mode, but with x-google-backend defined to configure timeouts per route.

Historically, ESPv2 could not handle per-route configs when running in sidecar mode (for GKE/GCE). It was only usable when running in remote proxy mode (for serverless platforms).

This example validates per-route configs in sidecar mode.