bug: synchronize id for ooni and dw descriptor IDs in prod and dev environments.

[aanorbel]

Describe the bug

• OONI and NMS Descriptors dont have thesame ID in both development and production

To Reproduce

Steps to reproduce the behavior.

These links should match in both environments.

DW

• https://api.ooni.org/api/v2/oonirun/links/10004 >> https://api.dev.ooni.io/api/v2/oonirun/links/10004
• https://api.ooni.org/api/v2/oonirun/links/10005 >> https://api.dev.ooni.io/api/v2/oonirun/links/10005
• https://api.ooni.org/api/v2/oonirun/links/10006 >> https://api.dev.ooni.io/api/v2/oonirun/links/10006

OONI

• https://api.dev.ooni.io/api/v2/oonirun/links/10470
• https://api.dev.ooni.io/api/v2/oonirun/links/10471
• https://api.dev.ooni.io/api/v2/oonirun/links/10472
• https://api.dev.ooni.io/api/v2/oonirun/links/10473
• https://api.dev.ooni.io/api/v2/oonirun/links/10474

Expected behavior

• The links mentioned above should be thesame in both environments
• OONI Descriors should have an ID between 00000 and 10000

[DecFox]

The following internal oonirun IDs have been reset to the following

https://api.dev.ooni.io/api/v2/oonirun/links/10004 -> https://api.dev.ooni.io/api/v2/oonirun/links/00101
https://api.dev.ooni.io/api/v2/oonirun/links/10005 -> https://api.dev.ooni.io/api/v2/oonirun/links/00102
https://api.dev.ooni.io/api/v2/oonirun/links/10006 -> https://api.dev.ooni.io/api/v2/oonirun/links/00103
https://api.dev.ooni.io/api/v2/oonirun/links/10470 -> https://api.dev.ooni.io/api/v2/oonirun/links/00104
https://api.dev.ooni.io/api/v2/oonirun/links/10471 -> https://api.dev.ooni.io/api/v2/oonirun/links/00105
https://api.dev.ooni.io/api/v2/oonirun/links/10472 -> https://api.dev.ooni.io/api/v2/oonirun/links/00106
https://api.dev.ooni.io/api/v2/oonirun/links/10473 -> https://api.dev.ooni.io/api/v2/oonirun/links/00107
https://api.dev.ooni.io/api/v2/oonirun/links/10474 -> https://api.dev.ooni.io/api/v2/oonirun/links/00108

The following links should now give same results for prod and dev:

• https://api.ooni.org/api/v2/oonirun/links/10004 : https://api.dev.ooni.io/api/v2/oonirun/links/10004
• https://api.ooni.org/api/v2/oonirun/links/10005 : https://api.dev.ooni.io/api/v2/oonirun/links/10005
• https://api.ooni.org/api/v2/oonirun/links/10006 : https://api.dev.ooni.io/api/v2/oonirun/links/10006

[aanorbel]

Hi @DecFox , is there a particular reason why the OONI Descriptors cant start with a whole number? 00100 - 00104 would have been preferable

• https://api.dev.ooni.io/api/v2/oonirun/links/00104 (Websites)
• https://api.dev.ooni.io/api/v2/oonirun/links/00105 (Instand messaging)
• https://api.dev.ooni.io/api/v2/oonirun/links/00106 (Circumvention)
• https://api.dev.ooni.io/api/v2/oonirun/links/00107 (Performance)
• https://api.dev.ooni.io/api/v2/oonirun/links/00108 (Experimental)

[hellais]

is there a particular reason why the OONI Descriptors cant start with a whole number?

Why do we need the OONI Run link ids having a fixed length? OONI Run link IDS should in theory be extensible beyond 99999 and as per spec they should be treated as a string (that means that 00104 is different than 104).

[aanorbel]

The above examples were following a pattern recognized in the existing OONI Run link IDS.

At the moment, https://api.dev.ooni.io/api/v2/oonirun/links/104, and https://api.dev.ooni.io/api/v2/oonirun/links/00104 are quite different with the former(104) returning a 404. The later returning the actual response.

[hellais]

This is done for DW and we can create a new one for the OONI app in the future