gaborgsomogyi opened a new pull request #16463: URL: https://github.com/apache/flink/pull/16463
## What is the purpose of the change At the moment there is no possibility to influence netty HTTP inbound/outbound requests. This could be useful from many perspectives. A good example (amongst others) is authentication/authorization. Here are the exact examples: * With an outbound custom netty handler one can modify the HTTP request by adding authentication information. * With an inbound custom netty handler one can do authentication/authorization. In this PR I've added 2 generic APIs in order to handle inbound and outbound HTTP requests. Please see [FLIP-181](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=184616200) for further details. ## Brief change log * Added. `InboundChannelHandlerFactory` * Added. `OutboundChannelHandlerFactory` * `TestRestServerEndpoint` and `RestClient` are now getting Flink `Configuration` instances. ## Verifying this change * Existing automated tests * There are 2 not yet published external repositories with automated tests using the newly added APIs: * Basic authentication * Kerberos authentication ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): no - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: yes, introduced 2 `@Experimental` APIs - The serializers: no - The runtime per-record code paths (performance sensitive): no - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no - The S3 file system connector: no ## Documentation - Does this pull request introduce a new feature? yes - If yes, how is the feature documented? JavaDocs + API usage examples (intended to be published when APIs are in place) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
