One of the upcoming features of apps requires access to liftwing.
Currently we don't have a service mesh connection configured that allows connection between PCS and liftwing.
What would be the next steps to achieve that?
One of the upcoming features of apps requires access to liftwing.
Currently we don't have a service mesh connection configured that allows connection between PCS and liftwing.
What would be the next steps to achieve that?
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T427425 [Epic] Apps Year in Review 2026 (V4) | |||
| Resolved | Dbrant | T429634 [Android] Implement Topics for articles in reading history for Year in Review | |||
| Resolved | Clement_Goubert | T431108 Service mesh configuration to allow PCS to connect to liftwing |
@Dbrant the service we want is liftwing, right? Can you provide some example request?
I believe so; More details about the service url are here:
https://phabricator.wikimedia.org/T392833#11987986
And here is an example request:
curl https://linked-artifacts.discovery.wmnet:30443/revisions/v1/article_topics/enwiki/534366/1358198637
...where the parameters in the path are .../[wiki]/[pageid]/[revisionid]
It is indeed the linked-artifacts cache (or LAC). Example requests can be found in https://phabricator.wikimedia.org/T392833#11987986 and more documentation is available on the LAC wikitech page.
The clients (PCS in this case) makes requests to LAC and LAC makes the requests to LiftWing whenever there is a cache miss
Change #1308605 had a related patch set uploaded (by Clément Goubert; author: Clément Goubert):
[operations/puppet@production] linked-artifacts: service::catalog to production
Change #1308604 had a related patch set uploaded (by Clément Goubert; author: Clément Goubert):
[operations/puppet@production] linked-artifacts: Add service catalog and mesh entries
Change #1308609 had a related patch set uploaded (by Clément Goubert; author: Clément Goubert):
[operations/deployment-charts@master] mobileapps: Add linked-artifacts mesh listener
Change #1308604 merged by Clément Goubert:
[operations/puppet@production] linked-artifacts: Add service catalog and mesh entries
Change #1308609 merged by jenkins-bot:
[operations/deployment-charts@master] mobileapps: Add linked-artifacts mesh listener
Change #1308605 merged by Clément Goubert:
[operations/puppet@production] linked-artifacts: service::catalog to production
You should now be able to reach linked-artifacts through the service mesh, using http://localhost:6074 as a base URL, so curl https://localhost:6074/revisions/v1/article_topics/enwiki/534366/1358198637
Feel free to reopen if you encounter any issue.
Change #1309712 had a related patch set uploaded (by Scott French; author: Scott French):
[operations/puppet@production] linked-artifacts: Use /healthz handler in blackbox probes
Change #1309712 merged by Scott French:
[operations/puppet@production] linked-artifacts: Use /healthz handler in blackbox probes
Change #1320156 had a related patch set uploaded (by Jgiannelos; author: Jgiannelos):
[operations/deployment-charts@master] mobileapps: Define request template for linked artifacts endpoint
Change #1320156 merged by jenkins-bot:
[operations/deployment-charts@master] mobileapps: Define request template for linked artifacts endpoint