deploy probe-services v2 in production

ooni / probe

OONI Probe network measurement tool for detecting internet censorship

https://ooni.org/install

BSD 3-Clause "New" or "Revised" License

754 stars 142 forks source link

deploy probe-services v2 in production #2781

Open ainghazal opened 1 month ago

ainghazal commented 1 month ago

The openvpn experiment depends on the newer endpoint we deployed a few months ago in the staging backend. To be able to test the release candidates, we need to deploy the service in production.

hellais commented 1 month ago

For an MVP can we just hardcode some endpoints in the test that we know are going to be stable? I don't think it's realistic to assume probe services v2 will be in production by the rollout of the experiment.

ainghazal commented 1 month ago

there were a couple openvpn endpoints hardcoded; they were removed to ensure API can control switching off the experiment by delivering an empty list (possibly by country);
it's possible to re-add those default endpoints
the credentials problem remains unsolved; we cannot hardcode them in a production client (since they will expire); that was the reason that drove the VPN endpoint in the first place.

ainghazal commented 1 month ago

fwiw, the experimental card simply does not run the OpenVPN experiment if the API returns an error. So perhaps it's feasible to ship it and just enable the service whenever it's possible.