Todd Baert

I only see one small issue: the way `GLUE_PROPERTY_NAME` name works, for example [here](https://github.com/open-feature/java-sdk-contrib/pull/1008/files#diff-1151aff13c6105b60e85b16a2b7dc29ebf06b24bae2d4f75f348dde26a5f208aR23), it resolves all subclasses under that package: so your `RunFlagdInProcessEnvoyCucumberTest` class is running BOTH the `dev.openfeature.contrib.providers.flagd.e2e.process.envoy.FlagdInProcessSetup`...

@pradeepbbl I merged another PR that results in some (I believe minor) conflicts here, mostly with the setup of the providers for e2e tests. Just be sure to use: ```java...

https://github.com/open-feature/java-sdk-contrib/pull/1022#issuecomment-2417567334

> Currently cannot upgrade to this version, since it is not supporting Java 8. I guess we can now? @liran2000

> What if the permission denied started happening after the provider initialized? Going to PROVIDER_FATAL state would mean the Open Feature won't be able to evaluate any flags, right? And...

@alan-kut the built-in gRPC retry policy [already has a backoff](https://grpc.io/docs/guides/retry/), so if we give the ability to customize the retriable codes, we have some ability to use that backoff without...

> I tried to find more details but as far as I understand it only work for the stream initialization, not for the first Recv() which is in line with...

> Going into FATAL on certain codes ONLY in the first sync cycle as @alan-kut pointed out > I would suggest I update my PR https://github.com/open-feature/go-sdk-contrib/pull/799 accordingly & we should...

@wichopy if you are still interested in this I can assign you.

Another option I was thinking about is that we could deprecate this RPC entirely, and add it to the content of the sync itself... so instead of the [SyncFlagsResponse](https://buf.build/open-feature/flagd/docs/main:flagd.sync.v1#flagd.sync.v1.SyncFlagsResponse) just...