move to tool - draft - cont.

Signed-off-by: liran2000 <[email protected]>

Author: liran2000

providers/flagd/README.md

@@ -54,45 +54,6 @@ The value is updated with every (re)connection to the sync implementation.
 This can be used to enrich evaluations with such data.
 If the `in-process` mode is not used, and before the provider is ready, the `getSyncMetadata` returns an empty map.
 
-#### Http Connector
-HttpConnector is responsible for polling data from a specified URL at regular intervals.  
-It is leveraging Http cache mechanism with 'ETag' header, then when receiving 304 Not Modified response,
-reducing traffic, reducing rate limits effects and changes updates. Can be enabled via useHttpCache option.  
-The implementation is using Java HttpClient.
-
-##### Use cases and benefits
-* Reduce infrastructure/devops work, without additional containers needed.  
-* Use as an additional provider for fallback / internal backup service via multi-provider.
-
-##### What happens if the Http source is down when application is starting ?
-
-It supports optional fail-safe initialization via cache, such that on initial fetch error following by 
-source downtime window, initial payload  is taken from cache to avoid starting with default values until 
-the source is back up. Therefore, the cache ttl expected to be higher than the expected source 
-down-time to recover from during initialization.
-
-##### Sample flow
-Sample flow can use:
-- Github as the flags payload source.
-- Redis cache as a fail-safe initialization cache.
-
-Sample flow of initialization during Github down-time window, showing that application can still use flags 
-values as fetched from cache.
-```mermaid
-sequenceDiagram
-    participant Provider
-    participant Github
-    participant Redis
-    
-    break source downtime
-        Provider->>Github: initialize
-        Github->>Provider: failure
-    end
-    Provider->>Redis: fetch
-    Redis->>Provider: last payload
-
-```
-
 ### Offline mode (File resolver)
 
 In-process resolvers can also work in an offline mode.
@@ -113,17 +74,15 @@ This mode is useful for local development, tests and offline applications.
 #### Custom Connector 
 
 You can include a custom connector as a configuration option to customize how the in-process resolver fetches flags. 
-The custom connector must implement the [QueueSource interface](https://github.com/open-feature/java-sdk-contrib/blob/main/providers/flagd/src/main/java/dev/openfeature/contrib/providers/flagd/resolver/process/storage/connector/QueueSource.java).
+The custom connector must implement the [Connector interface](https://github.com/open-feature/java-sdk-contrib/blob/main/providers/flagd/src/main/java/dev/openfeature/contrib/providers/flagd/resolver/process/storage/connector/Connector.java).
 
 ```java
-QueueSource connector = HttpConnector.builder()
-    .url(testUrl)
-    .build();
+Connector myCustomConnector = new MyCustomConnector();
 FlagdOptions options =
-    FlagdOptions.builder()
-        .resolverType(Config.Resolver.IN_PROCESS)
-        .customConnector(myCustomConnector)
-        .build();
+        FlagdOptions.builder()
+                .resolverType(Config.Resolver.IN_PROCESS)
+                .customConnector(myCustomConnector)
+                .build();
 
 FlagdProvider flagdProvider = new FlagdProvider(options);
 ```

tools/flagd-http-connector/src/test/resources/simplelogger.properties

@@ -1,3 +1,3 @@
-org.org.slf4j.simpleLogger.defaultLogLevel=debug
+org.slf4j.simpleLogger.defaultLogLevel=debug
 
 io.grpc.level=trace