"As a Client Developer, I want to have a single root domain for API calls, so that I don't have to manage different roots in my code."
We'd like to get api.wiki[mp]edia.org
"As a Client Developer, I want to have a single root domain for API calls, so that I don't have to manage different roots in my code."
We'd like to get api.wiki[mp]edia.org
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
api-gateway: enable TLS when talking to appservers | operations/deployment-charts | master | +65 -33 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | • eprodromou | T235270 Wikimedia API Gateway | |||
Resolved | • eprodromou | T255030 Wikimedia API Gateway MVP | |||
Resolved | hnowlan | T235272 Client Developer has a preferred API server | |||
Resolved | • eprodromou | T254794 Envoy API Gateway Implementation | |||
Resolved | hnowlan | T254908 API Gateway LVS Endpoint | |||
Resolved | hnowlan | T254910 Metrics and dashboards for API Gateway | |||
Resolved | hnowlan | T254913 Integrate Envoy API Gateway into critical path | |||
Resolved | hnowlan | T254906 Basic Helm chart covering just Envoy, no rate limiting |
@hnowlan it would be great to know what the alpha endpoint is going to be.
Also, if there's something we need to do to get api.wikipedia.org and api.wikimedia.org to point to the gateway.
Change 618972 had a related patch set uploaded (by Hnowlan; owner: Hnowlan):
[operations/deployment-charts@master] api-gateway: enable TLS when talking to appservers
Change 618972 merged by jenkins-bot:
[operations/deployment-charts@master] api-gateway: enable TLS when talking to appservers