route validation

[aryszka]

Invalid route configuration, e.g. a typo in a filter's name or invalid arguments are currently detected only in the last phase of the route updates, and it's not possible to reuse Skipper's code for route validation in external processes.

A validation mechanism that works with the in-memory eskip representation of the routes, and can be used in the data clients or in external processes. To make it really nice, the filter and predicate specifications could optionally implement an interface that can validate the arguments without creating the active run-time representation of the filters and predicates, and if possible also can be used to generate documentation. It is expected that, besides just failing early, such a mechanism would make it easier to provided more meaningful messages about route configuration problems.

If this feature is shipped, the routing package should be reviewed, and cleaned up for potentially duplicate functionality (e.g. informative messages: https://github.com/zalando/skipper/blob/master/routing/datasource.go#L220)

[ruudk]

Permalink: https://github.com/zalando/skipper/blob/0cc8c24b726a3f2da11594c86b125dead0c324c3/routing/datasource.go#L220-L222

[szuecs]

This was fixed via validation webhook, but we need to add documentation for this. I have some local start that I will push hopefully soon.