[ 
https://issues.apache.org/jira/browse/FLINK-25866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17486119#comment-17486119
 ] 

Igal Shilman edited comment on FLINK-25866 at 2/2/22, 9:38 PM:
---------------------------------------------------------------

Great [~Fil Karnicki], I hope you'll get the necessary approvals soon.

 

Meanwhile, I was looking at the ResourceLocator class (you can find it at 
statefun-core), and it has what you will need. We use that exact class to 
locate the module.yaml, and it should work in this case as-well.

One thing to keep in mind is that it is always called with the context class 
loader set. This is important because sometimes the class loader that loads the 
runtime classes (for example the ResourceLoader itself) is a different than the 
class loader that is loading the user code. This might explain why you couldn't 
find any additional files previously.


was (Author: igal):
Great [~Fil Karnicki], I hope you'll get the necessary approvals soon.

 

Meanwhile, I was looking at the ResourceLocator class (you can find it at 
statefun-core), and it has what you will need. We use that exact class to 
locate the module.yaml, and it should work in this case as-well.

One thing to keep in mind is that it is always called with the context class 
loader set, and the class will chose the context class loader. This is 
important because sometimes the class loader that loads the runtime classes 
(for example the ResourceLoader itself) is a different than the class loader 
that is loading the user code. This might explain why you couldn't find any 
additional files previously.

> Support additional TLS configuration.
> -------------------------------------
>
>                 Key: FLINK-25866
>                 URL: https://issues.apache.org/jira/browse/FLINK-25866
>             Project: Flink
>          Issue Type: Improvement
>          Components: Stateful Functions
>            Reporter: Igal Shilman
>            Priority: Major
>
> Currently the default HTTP client used to invoke remote functions does not 
> support customising the TLS settings as part of the endpoint spec definition. 
> This includes
> using self-signed certificates, and providing client side certificates for 
> authentication (which is a slightly different requirement).
> This issue is about including additional TLS settings to the default endpoint 
> resource definition, and supporting them in statefun-core.
> User mailing list threads:
>  * [client cert auth in remote 
> function|https://lists.apache.org/thread/97nw245kxqp32qglwfynhhgyhgp2pxvg]
>  * [endpoint self-signed certificate 
> problem|https://lists.apache.org/thread/y2m2bpwg4n71rxfont6pgky2t8m19n7w]
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to