router-api annotations for gRPC services
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Motivation: gRPC should support annotations that help to configure the execution strategy per service or per route. Also, gRPC should compute the effective execution strategy based on the main execution strategy from the builder configuration and from the route configuration. Modifications: - Parse annotations from `route-api` module; - Compute difference between execution strategy on the builder and on the route; - Add tests to verify that offloading works correctly for different execution strategy configurations; - Add tests to verify that misconfiguration of `route-api` annotations will be explained to the user; - Adjust gRPC codegen for new features; - Fix tests; Result: gRPC routes correctly support per-route execution strategy configuration.
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge.