Change Details

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 `/v1/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 `/v1/summary/*` endpoints should just call mobile apps directly. --- [ ] Content Segment from `cxserver` (?) [ ] Endpoints involved are: [ ] `/v1/segment/{title}` [ ] `/v1/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 [ ] NOTE: The [[ https://gerrit.wikimedia.org/g/mediawiki/extensions/ContentTranslation/+/c9a96abd07853a48800a28932669e9d6b15eee0b/includes/RestbaseClient.php | RESTbase client code ]] is still there that will need to be deleted in the future. [ ] 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. [ ] Flow is using the `/v1/transform/*` endpoint: https://gerrit.wikimedia.org/g/mediawiki/extensions/Flow/+/d2048d9a92825e28276c8b29b191ba78c9afb26a/includes/Conversion/Utils.php#132 [ ] Popups extension uses the `/v1/summary/*` endpoint for page previews [ ] See https://gerrit.wikimedia.org/g/mediawiki/extensions/Popups/+/3573232c2168ef404762936e7176f1230365892c/README.md#51 (for example config) [ ] Also see: https://codesearch.wmcloud.org/search/?q=PopupsRestGatewayEndpoint for the config var. [ ] VEForAll extension calls RESTBase's `/transform/` endpoint: https://gerrit.wikimedia.org/g/mediawiki/extensions/VEForAll/+/cffa12abb85200e90b1cbc636325b1ec1a89a6af/includes/ApiParsoidUtilsOld2.php#133 [ ] Feeds (WIP)

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 `/v1/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 `/v1/summary/*` endpoints should just call mobile apps directly. --- [ ] Content Segment from `cxserver` (?) [ ] Endpoints involved are: [ ] `/v1/segment/{title}` [ ] `/v1/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 [ ] NOTE: The [[ https://gerrit.wikimedia.org/g/mediawiki/extensions/ContentTranslation/+/c9a96abd07853a48800a28932669e9d6b15eee0b/includes/RestbaseClient.php | RESTbase client code ]] is still there that will need to be deleted in the future. [ ] 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. [ ] Flow is using the `/v1/transform/*` endpoint: https://gerrit.wikimedia.org/g/mediawiki/extensions/Flow/+/d2048d9a92825e28276c8b29b191ba78c9afb26a/includes/Conversion/Utils.php#132 [ ] Popups extension uses the `/v1/summary/*` endpoint for page previews [ ] See https://gerrit.wikimedia.org/g/mediawiki/extensions/Popups/+/3573232c2168ef404762936e7176f1230365892c/README.md#51 (for example config) [ ] Also see: https://codesearch.wmcloud.org/search/?q=PopupsRestGatewayEndpoint for the config var. [ ] VEForAll extension calls RESTBase's `/transform/` endpoint: https://gerrit.wikimedia.org/g/mediawiki/extensions/VEForAll/+/cffa12abb85200e90b1cbc636325b1ec1a89a6af/includes/ApiParsoidUtilsOld2.php#133 [ ] Wikifeeds/Feed [ ] Brief overview: https://wikitech.wikimedia.org/wiki/Wikifeeds [ ] The `/page/random/summary` endpoint for example ends up calling `/page/html` [[ https://wikitech.wikimedia.org/wiki/Wikifeeds#/media/File:Wikifeeds_simplified_example_request_flow.png | which accesses Parsoid ]] to get the HTML of a page. [ ] Other endpoints will need to be investigated if they call Parsoid.

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 `/v1/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 `/v1/summary/*` endpoints should just call mobile apps directly. --- [ ] Content Segment from `cxserver` (?) [ ] Endpoints involved are: [ ] `/v1/segment/{title}` [ ] `/v1/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 [ ] NOTE: The [[ https://gerrit.wikimedia.org/g/mediawiki/extensions/ContentTranslation/+/c9a96abd07853a48800a28932669e9d6b15eee0b/includes/RestbaseClient.php | RESTbase client code ]] is still there that will need to be deleted in the future. [ ] 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. [ ] Flow is using the `/v1/transform/*` endpoint: https://gerrit.wikimedia.org/g/mediawiki/extensions/Flow/+/d2048d9a92825e28276c8b29b191ba78c9afb26a/includes/Conversion/Utils.php#132 [ ] Popups extension uses the `/v1/summary/*` endpoint for page previews [ ] See https://gerrit.wikimedia.org/g/mediawiki/extensions/Popups/+/3573232c2168ef404762936e7176f1230365892c/README.md#51 (for example config) [ ] Also see: https://codesearch.wmcloud.org/search/?q=PopupsRestGatewayEndpoint for the config var. [ ] VEForAll extension calls RESTBase's `/transform/` endpoint: https://gerrit.wikimedia.org/g/mediawiki/extensions/VEForAll/+/cffa12abb85200e90b1cbc636325b1ec1a89a6af/includes/ApiParsoidUtilsOld2.php#133 [ ] Feeds (WIP)Wikifeeds/Feed [ ] Brief overview: https://wikitech.wikimedia.org/wiki/Wikifeeds [ ] The `/page/random/summary` endpoint for example ends up calling `/page/html` [[ https://wikitech.wikimedia.org/wiki/Wikifeeds#/media/File:Wikifeeds_simplified_example_request_flow.png | which accesses Parsoid ]] to get the HTML of a page. [ ] Other endpoints will need to be investigated if they call Parsoid.