Skip to content

Commit

Permalink
Update provider/specs/client.md
Browse files Browse the repository at this point in the history
Co-authored-by: Mark Phelps <209477+markphelps@users.noreply.github.com>
Signed-off-by: Thomas Poignant <thomas.poignant@gmail.com>
  • Loading branch information
thomaspoignant and markphelps authored May 2, 2024
1 parent 9a1bd6b commit 5f65fc7
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion provider/specs/client.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ The `initialize()` function should follow those steps:
1. Make a GET request to the `/ofrep/v1/configuration` endpoint to retrieve the configurations return by the flag management system and store them in memory to be available for all the function of the provider. *(See [Annexe 1](#annexe-1) for the description of the endpoint response)*
2. Make a POST request to the `/ofrep/v1/evaluate/flags` endpoint with the evaluation context in the body.
- If the endpoint returns an error, the `initialize()` function must error and exit.
- If the endpoint is in success, we should store in a local cache all the flags evaluation result returned by the API in a local cache. We should also store the `ETag` header in the provider to be able to send it back later.
- If the request is successful, we should store in a local cache all of the flags evaluation results returned by the API in a local cache. We should also store the `ETag` header in the provider to be able to send it back later.
3. If polling is enabled, the function should start the polling loop *(See [polling section](#polling))*.

## Evaluation
Expand Down

0 comments on commit 5f65fc7

Please sign in to comment.