Adriano Santos

Hi @omidb Would the idea here be to have access to ActorSystem? If so it would be easy to implement because it would expose the actorySystem property of the CloudStateRunner...

I think what you want is a mix of the two things I said.

Why not leave it to the underlying infrastructure at the user level? I see most people delegating such concerns to the kubernetes layer itself and things like authproxy, or keycloak...

I understand that there would be no easy way to propagate this to the application level, sidecar, if that's the approach. Maybe they are mutually exclusive approaches.

Judging by these logs it seems to me that the proxy is not activating the entity first.

Example Given a gRPC service defined as below: ```proto service TagService { rpc GetTags(GetTag) returns (stream Tag) { option (google.api.http) = { get: "/tags/{issuer_id}" } }; } } ``` And...

@viktorklang Yes. The ideal would be to be negotiable

Very nice @viktorklang , I am following your branch :) I will try to test this as it is. Thank you

Awesome @marcellanz

Hello @michaelpnash I think the first step would be to provide a way to run the proxy locally and with a transparent network between it and the user's function. So...