https://stream.wikimedia.org/?doc returns the following text:
Unable to render this definition swagger and openapi fields cannot be present in the same Swagger or OpenAPI definition. Please remove one of the fields. Supported version fields are swagger: "2.0" and those that match openapi: 3.0.n (for example, openapi: 3.0.0).
It should return a working documentation.
Change 524027 had a related patch set uploaded (by Ottomata; owner: Ottomata):
[mediawiki/services/eventstreams@master] Use openapi 3.0.0 instead of swagger 2.0
Change 524027 merged by Ottomata:
[mediawiki/services/eventstreams@master] Use openapi 3.0.0 instead of swagger 2.0
Change 524032 had a related patch set uploaded (by Ottomata; owner: Ottomata):
[mediawiki/services/eventstreams/deploy@master] Use openapi: 3.0.0 instead of swagger 2.0 in eventstreams spec.yaml template
Change 524032 merged by Ottomata:
[mediawiki/services/eventstreams/deploy@master] Use openapi: 3.0.0 instead of swagger 2.0 in eventstreams spec.yaml template
Mentioned in SAL (#wikimedia-operations) [2019-07-17T21:07:35Z] <otto@deploy1001> Started deploy [eventstreams/deploy@dbc9bbb]: Fix ?doc to use openapi instead of swagger - T227958
Mentioned in SAL (#wikimedia-operations) [2019-07-17T21:10:28Z] <otto@deploy1001> Finished deploy [eventstreams/deploy@dbc9bbb]: Fix ?doc to use openapi instead of swagger - T227958 (duration: 02m 52s)
Thank you! Fixed. This was caused by an update to the service-template-node version we used. spec.yaml used by ?doc was not updated properly.
Hm, I think varnish still has /?spec cached on some frontends. Not sure how long it takes for that to get purged, but I assume it eventually will.
Is component documentation supposed to contain nothing? In fact, there are multiple React errors on doing any action on the page. (Firefox 68.) Sorry if that’s a topic for a new task, the page still is effectively not working, just in a different way.