Currently, when feature flags are refreshed, we first make a request to fetch the Key and ETag for all feature flags. Then we compare it to the ETag for the feature flags that are currently in the client configuration. The expected behavior is to fetch the updated values of the feature flags only if we detect a change in the 'ETag' for one or more feature flags. However, the current code has a bug where the feature flag values are being fetched even when no change is detected based on the ETag comparisons. This item tracks fixing that bug, so we make a single request instead of two requests to refresh the feature flag values when no change is detected.
Currently, when feature flags are refreshed, we first make a request to fetch the
KeyandETagfor all feature flags. Then we compare it to theETagfor the feature flags that are currently in the client configuration. The expected behavior is to fetch the updated values of the feature flags only if we detect a change in the 'ETag' for one or more feature flags. However, the current code has a bug where the feature flag values are being fetched even when no change is detected based on theETagcomparisons. This item tracks fixing that bug, so we make a single request instead of two requests to refresh the feature flag values when no change is detected.