Open jaeddy opened 3 years ago
Also, because we probably shouldn't overwrite the current 1.0.0
tag/release (it's archived in Zenodo too...), I propose describing the versions for files under /openapi/v1/
(and similarly, in the future, keeping any x.0.y
patch spec files under the respective folder). By extension, I'd like to rename the version with service-info
as 1.1.0
and keep it under the base /openapi/
as our "latest" spec. I'll try to add some docs for this versioning approach as well.
:+1: Think we headed down this route with https://github.com/ga4gh/tool-registry-service-schemas/issues/82
Based on #134, the idea would be to create a folder
/openapi/v1/
, which would include:workflow_execution_service.swagger.yaml
workflow_execution_service.openapi.yaml
The
swagger.yaml
file would be the OpenAPI 2.0 version currently published under the1.0.0
release. As we never provided a OpenAPI 3.0 version for that release, we'd ad theopenapi.yaml
(basically what's currently indevelop
as version1.0.1
without theservice-info
integration).With the bump to OpenAPI 3.0, we should also make sure that all models/components are correctly specified.