See parent task T218217: Make services swagger specs standard compliant
Blocked until T225707: Upgrade python-service-checker across the fleet is resolved
See parent task T218217: Make services swagger specs standard compliant
Blocked until T225707: Upgrade python-service-checker across the fleet is resolved
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | santhosh | T217747 cxserver's swagger spec fails to validate | |||
Resolved | • Pchelolo | T217881 Decide whether to keep violating OpenAPI/Swagger specification in our REST services | |||
Open | None | T218217 Make services swagger specs standard compliant | |||
Resolved | MSantos | T218220 Make mobileapps & proton swagger spec compliant |
Change 504079 had a related patch set uploaded (by MSantos; owner: MSantos):
[mediawiki/services/mobileapps@master] WIP: Use upstream swagger-ui
Change 504891 had a related patch set uploaded (by MSantos; owner: MSantos):
[mediawiki/services/chromium-render@master] Use upstream swagger-ui
Change 508825 had a related patch set uploaded (by MSantos; owner: MSantos):
[mediawiki/services/mobileapps@master] Use upstream swagger-ui
Change 508825 merged by jenkins-bot:
[mediawiki/services/mobileapps@master] Use upstream swagger-ui
Change 514414 had a related patch set uploaded (by MSantos; owner: MSantos):
[mediawiki/services/mobileapps@master] Update spec to OpenAPI 3.0
Change 504079 abandoned by MSantos:
Use upstream swagger-ui
Reason:
Patch sliptted into more than one change. When Ibea93c3b790f2624f63380a8bcde95221f438ced is merged all functionality here will be fulfilled.
Change 520273 had a related patch set uploaded (by MSantos; owner: MSantos):
[mediawiki/services/chromium-render@master] Update swagger spec to 3.0
Change 514414 merged by jenkins-bot:
[mediawiki/services/mobileapps@master] Update spec to OpenAPI 3.0
Change 520273 merged by jenkins-bot:
[mediawiki/services/chromium-render@master] Update swagger spec to 3.0
@Pchelolo and @mobrovac we tried to deploy mobileapps a while ago and service-checker complained about.
I'm marking this as stalled for now, but don't know the criteria to push these changes forward, could you outline those, please? Which means, what needs to be deployed/developed so we can change the services spec swagger version.
Service-checker supports swagger 3 definitions. Do you have any more info about what was in complained about?
Also, when upgrading RESTBase we found it useful to include a spec validity unit test.
Change 504891 abandoned by MSantos:
Use upstream swagger-ui
Reason:
This should be abandoned in favor of I07489ed86738fa0caedc897e6c06412f10e040ef
Mentioned in SAL (#wikimedia-operations) [2019-08-15T17:58:11Z] <mbsantos@deploy1001> Started deploy [proton/deploy@fb0b2a5]: Update chromium-renderer to 3f1cc72 (T218220)
Mentioned in SAL (#wikimedia-operations) [2019-08-15T17:58:53Z] <mbsantos@deploy1001> Finished deploy [proton/deploy@fb0b2a5]: Update chromium-renderer to 3f1cc72 (T218220) (duration: 00m 43s)
Change 530437 had a related patch set uploaded (by MSantos; owner: MSantos):
[mediawiki/services/chromium-render@master] Fix: swagger spec x-amples schema
Change 530437 merged by jenkins-bot:
[mediawiki/services/chromium-render@master] Fix: swagger spec x-amples schema