See:
This could be done as part of the build/deploy process with static html, or could be done using via a dyanamic route. Not sure which is better.
See also: https://github.com/OAI/OpenAPI-Specification/issues/396 for fixing 'no response' spec error
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | Xqt | T125197 Give hint to the current socketIO_client in ImportError of rcstream.py | |||
| Declined | None | T91393 RCStream is not accessible from python client due to using socket-io 1.0 while only socket-io 0.9 is offered | |||
| Declined | None | T68232 Upgrade RCStream backend to use socket.io 1.0 protocol | |||
| Resolved | Ottomata | T130651 EventStreams | |||
| Resolved | Ottomata | T158066 Create EventStreams swagger spec docs endpoint |
Change 338284 had a related patch set uploaded (by Ottomata):
[WIP] Serving Swagger UI spec docs at /doc
Change 340187 had a related patch set uploaded (by Ottomata; owner: Ottomata):
Configure a /v2/schema/* endpoint that reads schemas out of local filesystem
Change 340235 had a related patch set uploaded (by Ottomata; owner: Ottomata):
Update spec.yaml.js template to match eventstreams'
Change 340235 merged by Ottomata:
Update spec.yaml.js template to match eventstreams'
Change 340246 had a related patch set uploaded (by Ottomata; owner: Ottomata):
Only pipe /v2/stream requests to EventStreams service, everything else can be cached by varnish
Woot, its working! https://stream.wikimedia.org/?doc
Wikitech docs updated here: https://wikitech.wikimedia.org/wiki/EventStreams#API
We should only pipe directly to the service for streams, everything else can be cached as usual by varnish. Patch for review here: https://gerrit.wikimedia.org/r/#/c/340246/
Change 340246 merged by Ottomata:
[operations/puppet] Only pipe /v2/stream requests to EventStreams service, everything else can be cached by varnish
Change 340187 abandoned by Ottomata:
Configure a /v2/schema/* endpoint that reads schemas out of local filesystem