The result of this task will be a list of services that accesses Parsoid via RESTBase in order to know which ones to begin migrating to access Parsoid via core.
NOTE: See Envoy Telemetry (k8s) graphana board: https://grafana.wikimedia.org/d/b1jttnFMz/envoy-telemetry-k8s?orgId=1&var-datasource=thanos&var-site=codfw&var-prometheus=k8s&var-app=All&var-destination=restbase&var-destination=restbase-for-services&var-destination=restbase_cluster
---
[ ] Mobile Apps (PCS) - Page content service is already doing this and Yiannis is looking (?) into it. Cc @Jgiannelos
[X] The `/summary/*` endpoints is now a pass through to mobile apps so any service that calls these endpoints end up in mobile apps and mobile apps will do the right thing. Preferably, services that call the `/summary/*` endpoints should just call mobile apps directly.
---
[ ] Content Segment from `cxserver` (?)
[ ] Endpoints involved are:
[ ] `/segment/{title}`
[ ] `/segment/{title}/{revision}`
[ ] MediaWiki with VirtualRestService from `mediawiki` appservers: VisualEditor, Flow, Math etc.
[X] ContentTranslation (CX) has already been migrated, see: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ContentTranslation/+/859459
[ ] VisualEditor is on the way of complete migration to use Parsoid directly. It's still using VRS clients until full switch flip.
[ ] Flow and Math are still to be migrated.
[ ] ...