You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
ainghazal
added
bug
Something isn't working
triage
chore
routine tasks that must be done, but require little active brain power
and removed
bug
Something isn't working
labels
Jul 19, 2024
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.
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.
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.
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.
The text was updated successfully, but these errors were encountered: